..DB and logs which aren't being backed up and therefore not quiesced.
I believe that it is quiesced no matter what, as queiscing targets application VSS writers and not specific disks.
If this KB still applies, you could try to exclude the SqlServerWriter from the quiecing triggered by the VMTools.
https://kb.vmware.com/s/article/1031200
You can also look into Commvaults AppAware VM snaps. This orchestres VM snaps along with an in- guest SQL backup agent.
With this you can also do PIT restores as SQL transaction logs are backed in the traditional way using a separate schedule. When you do a PIT restore of the VM, transaction logs are then applied automatically within the same job.. Though this is another beast, it might be what's needed in your scenario.
Just ideas..
/Rubeck