Probably some clarification would be good in terms of why do you want a RAW backup (I guess you mean flat copies of VM files as they are on datastore).
I'm going to make a wild guess - you are trying to prepare for the "smoking hole" scenario when almost everything is destroyed. After disaster you have set up a new piece of infrastructure, some ESXi servers and some storage space. Now you do have your Veeam backups available (.vbk and .vib/.vrb files) and need to restore a couple of critical VMs ASAP. Your new infrastructure does not have a Veeam Backup Server yet so you can't read the contents of the backups and provisioning a new Veeam server / proxies takes too much time to fit within RTO for your critical VMs.
If this is the case, you could use the extract utlity that allows extracting RAW VM files directly from .vbk (no need to have any Veeam products installed). Here is some more info: https://helpcenter.veeam.com/backup/hyperv/extract_utility.html
Extract the files from backup, copy to datastore, register the VM and power on.
Just one gotcha - extract utility only retrieves data from .vbk files - full backups. It would not be able to apply increments (.vib's or .vrb's). Therefore if you are preparing for this scenario, probably would make sense going with reverse incremental backup method for VMs in scope.
Alternatively you could set up a replication of some kind, either Veeam's or vSphere Replication, however in this case you would need to replicate to a Datastore.
Hope this helps.