Gotcha!
Well thanks so much for working this idea through with me. This is amazing!
Would still be interested in seeing a parameter locking function per pipeline that sends the set values through for more of a switching mentality between the same CC message in multiple pipelines. That could be super nice for pulling more functionality out of one cc message (on the same channel).
My colleague and I were talking about how if you wanted to use the same control fader to set different values per pipeline, you could just map the cc message make the cc value adjustment on one pipeline, unmap to keep that value intact and the same, then map the same cc controller and same cc message, make the value adjustment on the new pipeline… rinse and repeat for as many pipelines you want to use. Is there a mapping/unmapping function for the map/unmap buttons? LOL 
Thanks again, will dig into this work flow and let you know how it goes!
Nick