I didn't want to leave your thorough post without a reply, but I also wanted to be honest about expectations. I'm glad you shared this, because it's a new concept to me regarding how some shared cockpit applications work. Like anything that is shared with me, I try to keep it in mind while designing new aircraft systems; however, making a change like this across all my aircraft would probably required editing ~70 files, a couple hours of testing across platforms, and documenting my changes. I make similar changes to my entire fleet frequently, but I like to do them universally, for all interactions, and across all aircraft. Otherwise, I will end up duplicating my work when someone else asks about a specific event for another piece of equipment in another aircraft. I've been trending that way over time, but I know there are still a few instances of the old method in my new aircraft too.
I will absolutely keep this in mind, and try to be conscious of this in the future, but I didn't want you to think that I was ignoring a simple request either. I hope that makes sense, and that my explanation is clear. Finally, I would be happy to help you create your own solution if you were willing to be adventurous with editing code. Just because it would take a lot of effort for me to make this change to all my aircraft and push updates to all platforms/marketplaces doesn't mean you can't have the exact solution you're looking for in the meantime!