Design ideas for Veeam Backup Replication in three DC

Hello,

I was hoping to get some second opinions on a design for the following scenario. I'd really appreciate any insight.

We have a new VVF instance that will be composed of two storage arrays (served via FC) with 4 nodes per DC (two DCs total).

In both of these DCs we also have additional backup servers composed of local storage.

DC1 - this server additionally has an HBA for Direct SAN access and an HBA for a TL1000 Tape Library.
DC2 - this server has no HBAs, just local storage.
DC3 - this site has only a Data Domain with RL enabled.

Since we are unable to get another physical server for VBR alone, we have to put VBR on one of these servers.

My plan was to:

Use Hyper-V on the physical server in DC1 and create two VMs: one with Windows for VBR, and a second for LHR. This obviously has the downside of being virtualized, but we can restrict access to iDRAC only. Another downside is that we have to pass through both HBAs for it to work as a proxy, but that would allow us to use LHR as the primary repository (probably as a Scale-Out, as we have over 150 TB of space on that server). This approach adds a lot of complexity but gives us LHR.

Another option would be to simply install Windows on bare metal and use ReFS storage as the primary location. This would be much easier to maintain, but then we have no immutability on that repository.

However, since we will have a bare metal LHR in DC2 in addition to Tapes and Data Domain, I'm not really sure how important it is to have LHR on the first Veeam server as well.

The ideal scenario would be to use the new JeOS all-in-one appliance, but sadly that does not support acting as a proxy (to my knowledge).