It depends on what exactly you want to do.
My replies in
this thread explain the trade-off between the two available approaches: a remote control script and ad-hoc MIDI mapping.
The big plus of MIDI mapping is that you can link any parameter anywhere in your project to any controller on the spot, without rhyme or reason. One knob may control a filter cut-off somewhere deep in one track's device chain, while the next one is assigned to another track's third send dial. This is, if I understand correctly, what you want to do: pick out a few important parameters from all over you project and surface those, persistently, to a direct control.
(I do something like that with the F1-F8 buttons to turn my mastering effects chain on and off, and to switch on a device that simulates mono playback on a lo-fi speaker to quickly check my mix.)
You don't get that freedom with a remote control script, which defines controls more generally. The bank of eight channel strips will always behave as a group: all rotary encoders are assigned to panning, or to sends, or to a device's parameters.
On the other hand, what a script gets you is extended control as a middle man between Live and your hardware unit – including visual feedback like parameter names. If you press the PLUG-IN button on the X-Touch, you can select a Live device on the current track by pushing the corresponding encoder, and then all the parameters for that device are laid out over all the rotary knobs – with their names and values on the screens. But: you can't mix-and-match persistent controls from all over your project like with MIDI mapping. That's the trade-off.
Unfortunately, to my knowledge, the MIDI mapping system and the remote control scripts system don't talk to each other at all. As soon as you MIDI map a control, the script (with its ability to provide text feedback) is overruled for that particular knob/button/fader. So it's either MIDI mapping with total freedom, or the more generalized scripting with extended feedback like parameter names. You can't – again, to my knowledge – have an ad-hoc MIDI mapped control showing text feedback on the X-Touch.
As for your original problem ("all encoders of the same relative track on each of my X-Touch will control that parameter"), that should be solved if you check the Remote box in the MIDI settings (both Input and Output) for only one of your X-Touch units, right?