VADP Proxy selection should be more intelligent

During VMware backup VADP Proxies are selected by site and load, or you can assign a specific proxy (by name or site) to a VM that it should use for backup in the VM options.
In larger environments we have defined multiple vcenters to a single gui, each vcenter is running multiple ESX clusters.
We have deployed one or more VADP Proxies on each ESX cluster.
We have however not separated each vcenter or cluster into different sites, sites are defined as physical locations and policies build and assigned accordingly.
This means that a VM on cluster A can be in the same Site as a VM on cluster B.

If we do not assign a specific proxy to a VM we see that ISPP tries to backup a VM from cluster A using a proxy on Cluster B where cluster B can be in a different vCenter!
As storage and networks are separated, likely between ESX clusters but definitely between vcenters this backup will fail.

What we expect is that ISPP uses proxies on the same Cluster or vcenter as the VM, lets call it the "closest" proxy.

So please add additional options for the VADP selection process, if possible as defaults so we do not have to set it for each VM.

- Only use VADP Proxies on same cluster
- Only use VADP Proxies within same vcenter
- Use closest available proxy
- Only use VADP Proxies within same site (you already have this)
- Use any VADP Proxy