Any chance that a feature can be added to "Send to peer" that instructs the host to process messages from itself (via loopback). Something like a check box on the "Send to peer" event that says "Process host originated messages to itself".
Unless I'm missing something obvious...this causes a lot of redundant code between Peer and Host event groups that could be addressed in a common group if the host could be told to process it's own messages.
Again...apologies if I'm missing something obvious.
Since the host is the one sending the message, in the same event with the send to peer action you can add the actions for processing the message at the same time, since the host already has the data available.
Peers need to add the trigger on message received to trigger those actions, because there is a time delay until they actually receive the message. No point for the host to have this.
The redundant code would be having the same set of actions twice, once for peer and once for host. This is generally best practice, as in many situations host and peer are "interested" in different information and do different actions.
If you really want to consolidate your host and peer actions to be the same, call and use a function instead.