Another approach is to perhaps write a wrapper that will support ML on DLSR Controller App.
Keep the design simple: Run ML on the camera, and DLSR controller App on the Tablet. The idea is to run the wrapper on the Tablet, so as not to burden the camera processing one bit (except now it handles a few incoming USB commands).
The gain in functionality is: You can focus check on DSLR controller app, set AF points on the touch screen, and record. The rest is done on ML using its features, and these are sent as part of the picture to DSLR controller app. Not much is lost here.
You effectively gain ML display on a tablet size screen, and not so many features of DSLR controller app, but instead still trigger all your ML features from the camera LCD.
Then the only thing you have to use a wrapper (running on the tablet), is for three things:
1. update the full picture/display (usb RX from ML to DLSR controller),
2. AF point selection on touchscreen (usb TX from DSLR Controller app to ML), and
3. record (usb TX from DSLR controller app to ML).
A procedure:
* I guess download the canon SDK and see what tools you can use to monitor USB input/output *
- step one: map the picture/display output from the usb with Canon running standard.
- step two: load up ML, then repeat the exercise mapping the same output again.
- step three: write a wrapper that converts the canon ML display output to standard canon display output, as DSLR controller should now display the ML display output.
~~ Having run ML with EOS utility I do think ML can do this but I am not sure about its overlays, which would be needed since we are using ML and not DSLR controller for the features (focus peaks etc.)
- step four: map the AF touchscreen and record button output from DSLR controller app usb to a standard canon usb input.
- step five: get from ML its usb interface: I wonder if this had been disabled through hack??? Hopefully some inside folks know the answer. Anyways need to be able to trigger a ML record, and update AF (this is likely same as standard canon)
- step six: update the wrapper to covert DLSR controller usb outputs, back to ML equivalent commands. (hopefully some will document/wiki/provide)
- step seven: test and debug.
I think this is a lot more doable by keeping the design simple.
** THE TWO BIG QUESTIONS HERE ARE
1. CAN ML SEND ITS FULL DISPLAY INCLUDING OVERLAYS TO THE USB ?
2. CAN ML RECEIVE (RX) AF touchpoints and RECORD COMMANDS ON THE USB ? **
FYI Canon SDK's, written in C.
http://www.usa.canon.com/cusa/consumer/standard_display/sdk_homepage#SDKQ1 
