It's true that was a consequence of receiving them in separate rhsNodeRows, since the refactoring of the broadcaster some time ago.
However, it never used to be like this, in the past 1 node received from all (in an indeterminate order) and then broadcast back out the global set.

I think the fact that it (rhs) could remain globally ordered after the broadcaster refactoring was a side-effect, the main objectives were (afaicr) to avoid contention and to allow them to be freed as they were added to the HT. There was perhaps the idea to avoid having a large expanding ptr array too and size once all were known.
Anyway, I think allowing to remain RHS order deterministic was not the goal and wasn't the case before..

i.e. we never used to rely on rhs determinism, BUT in the non-failover SMART case it is.