This is where in a Network Session scenario where you have a client with the Remote Control password configured, the concept of 'Remote Control' starts to get a bit murky and confusing (similar to my DONE marker thread).
On the Client device, what information is just 'mirrored' from the Host (e.g. Playlist, Songs list) versus what still has a degree of local 'control' on the Client?
In this scenario, is Pressing the Play/Pause button on the Client sending a command to the Host much like a MIDI trigger or is it 'mirroring' or 'remote controlling' pressing Play/Pause on the Host. This is an important distinction as it can result in different actions.
Then throw in Global MIDI triggers - are they sent from the Client of Host? This might be incredibly important as it has a bearing how how you architect your MIDI setup. If you assume the Client is 'driving' the Host, but then discover the Global MIDI triggers are initiated from the Client device, you now have to think about adding that Client into your MIDI setup. Your audio tracks are coming from the Host device; why would the MIDI events come from the Client?
As seen above, there is even the line of thinking that the Client acts as a 'relay' - Client triggers something, Host responds and send it back to the Client, Client sends it to the rest of the MIDI setup.
There are a lot of ways people will approach thinking about this. Network Sessions and Remote Control is quite a powerful feature and it will definitely need some clear documentation when the time comes!