You should not use Hyper-V snapshots as a backup strategy for SQL. Stick with something (built-in or otherwise) that will backup SQL knowledge.
Hyper-V snapshots (in my opinion) should only be used on production servers for very quick recovery after a failure. If you are updating, take a picture first, check when it is done right away, then take a picture. Such things should be done next to your regular backups, and not instead of it.
If you want to go to Hyper-V snapshots as your only backup strategy, you will lose the opportunity to restore your database to another server and restore the database in a timely manner - among other things, I'm sure I just don't think about it now.