Any drawbacks to setting CONTROL_ML_LBUTTON to TRUE, TRUE?

I'm playing around with a gun script and in order to have more controls outside Mouselook, I had to combine my other control permissions with the CONTROL_ML_LBUTTON permission, which is typically set for the accept argument TRUE and pass-on set to FALSE. Now, to continue using controls for other functions outside of ML, those arguments are set to TRUE, TRUE

The thing is, everything appears to work like it should. I'm able to shoot in ML, and able to do my other actions outside of it, and neither mix up or impair the other. Or as it seems.

Is there a drawback to setting CONTROL_ML_LBUTTON to TRUE, TRUE instead of TRUE, FALSE that I'm not seeing, and if there is, how would I go about running the two seperate actions without one interfering with the other. I tried to seperate the llTakeControls two where there were two instances, one for TRUE, TRUE and the other for TRUE, FALSE, and was unable to fire in ML, but able to do the other actions.

The pass_on argument generally defines whether you're passing those commands to your avatar in addition to the object(s) you are controlling. At a guess, the pass_on for mouselook clicking would also trigger touch, drag, and other events by your avatar if the second argument is set to TRUE, whereas they would not when set to FALSE. And no, nothing should change when out of mouselook.

In terms of other uses, I use the pass_on parameter for my flight overrider, as it allows my avatar to lift off and fly normally while triggering the control event.