yes currently the buttons toggle with note on/off respectively.
This is contrary to the way the buttons work on the unit. i.e. once activated button effects remain in on state until button is depressed again.
In a midi sequencer scenario(especially live) the current set up requires more midi information to be stored and limits the ability of the sequencer to activate the button functions on the mp in a pseudorandom and/or generative manner.
Example: spin: a 6 step bar with a button on signal on step 1 and button off signal on step 4.
In the current way the mp responds to midi notes and the buttons, note length determines the length of the engaged effect. This means that must be programmed into the sequencer which means more time programming and more midi data to store. Also the length the button affect was engaged in a pseudorandom mode would always be the same.
If the mp had midi note c4 trigger spin on and c#4 off, now running the sequencer running in a pseudorandom mode would trigger on and offs at different intervals. e.g. sometimes the spin effect would stay on for 2 steps and others 12 or more possible.
I don’t see remembering the note#s being a problem. They would go in order just like they do now except the right adjacent note# would be off to its respective on. And once you get these values programmed into your sequencer or controller, you are really not going to mess with it. I have midi gear with on/off buttons that are controlled in the manner I described.
cc# would be fine but it would require that a certain cc# value range be on and off which seems more difficult to change but who knows.
My suggestion is just that the mp buttons respond to midi control in the same manner as they react on the mp surface. I have tried to imagine many cases where one may use a midi keyboard or other controller to remotely trigger the mp buttons in the current configuration and it seems cumbersome to use in each case.