Option 1 or 2 are both fine. The plus of Option 2 is that you don't have to remember to add new VMs to your backup jobs, but it also means you have to use one job to backup all your VMs, so if you need different backup job settings for different VMs, you can't do that.
If your Hyper-V hosts are in a cluster, then you want to make sure you add the cluster itself and not add each cluster node individually. Also, if you have SCVMM, then you'd want to add that to Veeam instead.
For 14 restore points, I would skip the weekly synthetic full and just use forever forward incremental. You will have one full backup along with the daily incrementals and they will get merged every day. Active Full isn't really required, but can be good as a precaution.
It's a personal preference on how often to do periodic active fulls, or to even do them at all. I've seen customers do it both ways. With such a short retention period, forever forward incremental is unlikely to experience an issue and even if it does there are many restore points after that corruption (since there are only 14 in the entire chain) to affect.
What I often suggest is in lieu of synthetics fulls, when dealing with chains < 30 RPs, is to use SureBackup. If you use that weekly or even daily you'll quickly discover if there's an issue at which point you can immediately run an active full to start the entire process over.