There’s an xRules example that you should be able to play around with right away:https://forum.renoise.com/t/new-tool-3-1-xrules/45670
That should give you an idea of one way to get rolling with TouchOSC, and perhaps see how to change things to suit you interests.
I can’t say if you’re headed to controller overload. OTOH, if you don’t already see how something is supposed to fit into your recording/composing/performance routine then there may be little reason to pursue it. But also believe that often you don’t know the value of something until you’ve played around with it.
One of the nice things about TouchOSC is that you can create your own control surfaces (in contrast to physical hardware, unless you build your own).
I’ve gotten great use out of Control (http://charlie-roberts.com/Control/) by creating my own screens. I prefer it to TouchOSC because it gives better control over definfin OSC address patterns. The downside is that it’s a bit flakey and (as best I can tell) notactivelymaintained.
I’ve also written a simple Android app to provide a flexible OSC controller. The ability to define a UI and OSC messages to suityourselfis a powerful option so I’d encourage exploring TouchOSC andgettingfamiliarwith what it can do with Renoise.