Anthony -
This is just an observation from an end-user's perspective ~
If the Maschine MKII is anything like the APC 40 (I'm not familiar with the Maschine MKII), a big part of the problem is the limited hard-coded buttons & dials on the MIDI controller itself.
There's actually a LOT of MIDI support in recent versions of QS, but you need a MIDI controller that is capable of sending consecutive MIDI note messages to be able to select the individual cues. With most programmable MIDI controllers or keyboards this isn't a problem, but with hard-wired controllers like the APC 40 it does present some limitations. (I go in somewhat in depth concerning these limitations in my thread on the APC 40 on PL, as well as mentioning a couple of work-arounds.)
As advanced as QS is, Beyond is definitely MANY layers ahead in capabilities, and one of the huge additional features is the extensive customizing that is opened up by PangoScript. The APC 40 template that Pangolin includes with recent Beyond releases (lots of PangoScript programming behind the scenes!) gets around the hardware limitations of the APC, and reassigns them to the cue grid (among many other things) that makes the hardware compatible with the Beyond interface.
Long-story short ~
There's probably a LOT you can do with your controller with QuickShow, but if the controller itself isn't programmable, you may need to use some sort of MIDI mapping utility (MIDI-Ox, Bome MIDI Translator, etc.) between the controller input and QuickShow.
Beyond can more than likely be programmed to support just about any controller out there for just about any purpose, but it may take some deep-diving into PangoScript to overcome any inherent hard-wired controller limitations. PangoScript takes a bit of "tinkering" to understand, but it is VERY powerful, and there's probably very little that can't be done when using it.
Just my nickel's worth...