Don't remember seeing your original question back in December, sorry you didn't get any answers sooner ...
I don't know much about it (have done replication and log shipping, but not really for this type of DR application), and we do have clients that use VM replication for DR, but their hardware people take care of that (so I have no useful knowledge) and the first we hear about it is when it cocks-up and we are asked to rescue the whole lot from conventional backups (that's a drama of course, but not the norm ...)
What I do know is that we have had to reconfigure the Backups to be to-network, instead of to-local-disks, because the replication of the VM was including all that, and it was killing bandwidth ... I regard backup-to-network as a more fragile process than to-local-disk, although the performance tests we have done have only added a few percent to the elapsed backup time (YMMV of course ...)
I remain sceptical that these clever failover systems are going to save the bacon on the day that they are needed, particularly in Shops that don't have gazillions of servers and heaps of skills - but I don't have an alternative suggestion.
Either way, I would want all mission-critical DBs running in FULL recovery model and Log backups running at no more than 1 minute interval, and LOG backups immediately copied to somewhat-more-remote storage in case the server breaks / building catches fire / etc. so that I had a conventional restore-from-backup Plan-B in my back pocket.