I can only speak for myself, but I started to categorize ideas & suggestions a while back.
And I update the topic whenever features are actually implemented - 3.1 and Redux are looking quite good in this regard:
https://forum.renoise.com/t/list-of-feature-suggestions-for-renoise/40515
Yes, in Renoise, instruments are bound to the MIDI controller - not the other way around. So if you load an instrument, it might specify a certain input. That’s cool, but it leaves room for the opposite approach:
This tool (which is 2.8 only, AFAIK) examined that type of workflow:
https://www.renoise.com/tools/midi-management-console
Would be interesting to revisit that idea, not as much for voice-doubling (although cool), but more for a quick overview and managing “performance templates”, like you point out.
Yes, it’s nice that someone made a tool. But things like this should IMO really be core functionality. Why? Well, because it guarantees functionality over time. The link you posted is a perfect example why the tools fail in this regard. The API is broken (read: not backwards compatible) with pretty much every update. If tool authors do not update their tools, the functionality is gone.
So, what I am trying to say is that tools are a great addition, but important functionality should not depend on them. And I am afraid I do get a bit the impression that as soon as something has been made available as a tool, it does not get much attention anymore by Taktik and crew (because: the functionality is kind of there…just use the tool). This is a subjective feeling I have, and might not reflect the real situation, though.
Anyway, just thought I’d share this thought.