With the old generic remote system (legacy) I’d simply ‘stack generic remotes’.
I.E. If I tried to have one event do multiple things in the same generic remote mapping, only the FIRST one in the list worked. However, if I just made a new generic remote set to listen to the same port and linked the same event to different DAW commands/instructions then they’d ‘both’ work.
Perhaps you could do something similar with the new MIDI Remote system.
Build two of them listening to the same port/device. Teach each to do different things when required.
I.E. If I wanted the MPC pad that sends C-1 on my MPK2 to do ‘two things at once’ remotely in Cubase…
I’d make TWO MPK2 remotes in Cubase. They’d both listen to the same MIDI input. The first instance might be pretty robust, with LOTS of events learned and linked to remote control stuff in the DAW. The second instance might be ‘mostly empty’ but for controls I want doing ‘multiple things with a single push’. In my second MPK2 remote, I’d simply link that pad to the ‘secondary DAW command’ for my C-1 MPC pad.
I haven’t fiddled with the new remote system in Cubase 12 much yet, but it seems like it didn’t want to let me connect the same port to more than one remote through the Cubase UI. Seems like I found a way though (by editing the desired port names in the remote script directly).
So, you might need to edit subsequent instances of a remote script with something like Visual Studio Code (or a text editor) to get more than one listening to the same device and active at the same time, but in theory, it should work.
I.E. I create two remote scripts in Cubase.
My MPK2 A (connects fine to the MIDI ports I want while building them). This is where I learn all of the controls and link them to stuff like the DAW transport. Mixing channels, whatever…
My MPK2 B (Won’t connect to something already in use, so I just point it to any ole MIDI ports I can, then edit the remote script, and change it to the same port as My MPK2 A). In this remote device, I don’t have much learned at all. Only the controls I want doing ‘two things at once’. If the exact order matters, then I’d make sure the one that should happen first is in the A map (They’ll still be on the same MIDI tick most likely, but if actual event order matters…I think it happens in the order that the remote maps were loaded).
At this point I can add stuff for just the controls I want doing ‘multiple things at once’ in the B remote.