ok i had a quick look:
- unless you want polyphony i don't think you need a sub patch in your case
- instead of the radio button you want a midi/in/cc i object with the CC number of your "cycle"button. the trigger output of that object should go into a logic/counter trig input, and the green o output of this counter object goes into the muxing objects.
now this part, sorry, but the grgammar makes me not understand again haha
*because (I think) if I want to control with different midi cc and note due to not able in parent patch(right?)
you don't need a sub patch either for different CCs, you can just add several cc i objects if you want to control several parameters by unique midid CCs...
the midi channel issues someone described as a possible problem above can also be fixed in the main patch by going to the patch settings and changing the midi channel.
if you still have issues with the incoming data i strongly recommend adding a midi monitor object as again someone else said before.
i also just now understood you made this as a convenient dj/soundystem siren thing, so for that case you definately don't need a polyphonic subpatch. and don't worry about efficiency cause this patch will probably barely scratch the 5% usage mark of an axoloti.
if you want to improve on efficiency and latency though, one advice would be to avoid any "patch" cables going upwards. search for "execution order" on this forum, all cables should ggo from left to right, top to bottom. you can achieve this by just rearranging your objects so they are side by side. (title bar counts here) and not above/below each other