This current photo, makes the case against NETWORK propagation delay, at least some.
You can see, as the signal or 'work' flow is from that electronic Base Controller, having small electric motor outputs. But the shaft, it simply connects, straight is best, down a 'series' line, on occasional bearings, in each distributed box.
I'm thinking, say, 20 msec to box #1, from controller, then 400 mSec, for a Station box out 20 feet away.
Then, internal switch swing times of typical 300 mSec plus ..
So might be, at end of string, 400 + 300 = 700 mSec.
And so, instead of playing '700', against 380 mSec,
I just throw hands up and say: " Do 1. 000 Seconds, for a few percent over what's needed, without case by case delay.
Often, with a 'Human', we can take 1 second, just pulling arm back, after pressing 'START'.
Cant see good, thru my intentional 'smoked plexiglass' boxes., But only one box, at a time, is with switch TIP gear engaged. All those other Stations, with their own main (un-engaged) gear it's just hard, sometimes, to conceptualize it all, so hard, while keeping some computer science function detail in mind.
But, so anyway, don't forget, the main method is to send, to excess, that one single impulse, of concern, trusting switching (or whatever) will be complete
Meanwhile, down the line, there, the Station switch performs an 'auto-stop', of sorts, self switching upon completion of some local task.
For example, when switch 'B' gets cleared, overflow after positioning completion, then proceeds to reset switch 'A'. So the box kind-of self disconnects components, for least drag but also so that function doesn't 'Do the UNDEAD' thing, later.