And that is correct for "Loop". Loop is so called "system state set", AZ Controller change it in sync with Cakewalk "loop". So this monitor can be anywhere in the Logic tab and the result will be the same.
"Mute" is different, there is no general Mute. Every strip has Mute button (and there are "Automatable mute" for strips and "Rude mute"...). So, there must be some way to tell which mute you want to control. In AZ Controller "Mute" is parameter you can make "current", using Strip Action. There you select the strip and the type of mute. Once "current", parameter can be used by Value and Monitor <parameter value> Actions. So in such case Monitor should be in the same Logic list, after Mute is selected.
For MIDI actions your solution is good general solution. It explicitly mention which MIDI message to send in which case. What I have mentioned is solution for Mute and Mackie: LED use the same MIDI message as the button send (some not Mackie controllers use different messages for buttons and corresponding LEDs), for such case there is <Use Ctrl MIDI> parameter for MIDI Action, instead of specifying it explicitly. And in Parameter Monitor (so, works for Mute but not for Loop) there is "value", so setting Value parameter of MIDI Action to "value" applies it.
