The idea of having master/slave instances of VeeamOne is appealing: one of the greatest benefits of VeeamOne for Enterprise (Service Providers specifically) is an ability to monitor both, vSphere and Hyper-V environments from a single pane of glass.
However, the common challenge would arise from the fact those environments meant to be monitored, reside within the isolated/firewalled networks, which makes it a dillemma to punch DNAT holes through their perimiters to gather the required data, where to monitor every and each component behind the firewall would require that kind of rule to exist not only for vCenter (in vsphere environment), but also for every single node/component to be accessible over the network, making it rather complicated to implement.
If the concept of mast/slave was to be adopted, with an ability to collect data locally (Proxy-like VeeamOne appliance) to ship data later on upstream, to the Master collector, the design for monitoring purposes would be much easier, as not only it simplifies network communications, but also allows to scale-out (sorta) the VeeamOne instances.
Product Architect @ SingleHop - Veeam Platinum Service Provider
VCAP-DCD, VCAP-DCA, VCP-NV
Veeam Certified Architect