IMO your post showed schematics of a possible MIDI network, but not what its intention was.
Let me try to explain what I ment by “workflow” … taking one of my setups as an example.
I like to work DAW-less for jamming and finding inspiration. For this I need one sequencer, supporting play back of mutliple tracks and pattern. To control other gear it shall provide clock, PGM changes, MIDI notes, and CCs. This sequencer shall also record me playing live on some keyboards, catch my ideas, and loop the pattern instantly after recording with a minimum of me having to push buttons. Menu diving is a no-go. Everything shall go smooth, easy, straight, and quickly.
Now … this setup is organised as follows:
The MPC is master clock and controller. All other instruments are synchronized and controlled directly from the MPC. To distribute all the MIDI from the MPC, I use the different outputs of the MPC and MIDI-Through devices.
Some of the synths have keyboards, which I want to play live and record all events to the sequencer on the fly. Those keyboards are connected to a midi merge device and the merged MIDI is routed into the MPC. Now I can play on the keyboards and record everything I do. The only thing left to consider is, to have either the MPC (which is my default solution) or the keyboards (local on) preventing MIDI-loops. The AR in this setup may receive notes, but may also be controlled by it’s own sequencer. The AR sequencer will be synchronised to the MPC. Patterns are created live during the playback of the other tracks and stored on the AR. Same goes for other Elektron boxes, if conncected to this setup.
Since I work with a MIDI-patch-matrix with the matrix in the middle of the MPC and the other gear, I can also use the OT as master changing roles with the MPC.