Goes hands in hand with my thru suggestions:
Is there a rationale for why Squarp decided to not enable clock to all virtual cables simultaneously in FW 3.10?
I think the assumption is, that the the connected virtual hub is either flexible enough to route the clock as necessary or on the other hand possibly too dumb/slow to handle multiple clocks without adding them together or something.
It makes sense to not send the clock to all the virtual cables to not overload the receiving device merge / router and to minimize the message latency / jitter.