Hi. Just a teaser to fend off disappointment:
I'm working on this. I hoped to have it sooner but there were, as usual, complications requiring some thought.
All settings in the midi remote dialog box will have port and channel, with 'learn' buttons.
You can choose 'any' port or channel (as it is now) or a single specific port and channel.
(Sorry, no multiple specific connections like our routing system. See below.)
In addition, there will be a 'value type' (trigger, momentary, toggle) for settings that need it (transport record etc.).
Hopefully I can get this done, barring any brick walls I might encounter.
I mentioned I was pondering whether the step record should instead take its input from the actual routes connected to a track.
But in the end this was not desirable. Routes are what is recorded to a track when recording. Using those same routes
for step recording would interfere and record unwanted notes that were not recognized as remote functions.
So the remote really does require its own separate 'routing' system.
But just like our midi-to-audio controller assignment dialog, a complete separate multiple routing system would be much too complicated.
So we'll allow only one specific port and channel.
(Ironically, IIRC my midi-to-audio assignment framework DOES actually support multiple routes, but implementing them
with graphics and controls user support and so on, would be complicated - and hopefully not really necessary so far.)
If you can think of any other functions that might benefit from remote capability, now's the time to speak up.
I can try to include them. Hey - be reasonable. 
So it is not useable for me...