vRops for Horizon Broker Agent on NLB'd Connection Servers

I'm installing the vRops for Horizon components into my existing v6.0.2 vRops instance.  The big question concerns the vRops for Horizon broker agent that goes on the View Connection server.  In my case, I have two Connection Servers (a master and a replica) in a Windows NLB configuration.
 
Can I only install the broker on one of the Connection Servers?  The documentation says one broker per pod, but doesn't mention anything about a pod with a load-balanced Connection Server.  If View Clients are coming into one of the load-balanced Connection Servers (the one that didn't happen to have the vRops for Horizon agent on it), do those View Client metrics not get sent to vRops?  I guess it's safe to assume that no metrics get sent at all if the Connection Server with the rRops for Horizon agent is down altogether (e.g., for maintenance or because of a failure).