@ulrik while it looks like unnecessary overhead to wrap a RNBO node into a network (we already had that discussion with Faust nodes), I think it will increase the maintainability of the system - I'm hardly using it myself so trying to keep the special handling to a minimum ensures the functionality in the long run.
Also I would have to add some kind of API & interface to the RNBO wrapper dialog which would basically be duplicating what we have in scriptnode already.
One workflow tool that I could think of that would be generally helpful would be a function that automatically wraps any node into a DSP network by creating the exact amount of parameters with the range and connect them - this is agnostic of the node type (so you can do this with Faust / RNBO / SNEX / C++ nodes) but will save you 99% of the boring work.
TLDR: I wouldn't hold my breath for a custom RNBO solution for this.