Hi ndeadly.
I've installed Atmosphere and Mission Control (the current release versions on github), and I've had mixed results when I use a Mad Catz C.T.R.L. R (model 32266) controller on my (not modchipped) launch Switch.
There are no issues pairing on the Change Order/Grip screen.
When I use a C.T.R.L. R that's had the Mad Catz firmware update to enable XInput, all the controls on the unit work in Mission Control except for the analogue triggers not being mapped to anything (instead of being ZL and ZR).
When I use a C.T.R.L. R that's factory out of box condition, the analogue sticks are completely unpredictable.
I'd like to work with you on this.
I own both XInput and stock C.T.R.L. Rs, and I'd be happy to run any tests or logs you need to get these pads working with the Switch. Please reply with instructions or PM me.
If you don't own any Mad Catz pads, you may not know that the C.T.R.L. R range is the Android-centric model and there are at least three different hardware variations: the standard controller, the Micro mini version and the M.O.J.O branded variant. (All of these take different firmware images internally, so they may work differently.)
The C.T.R.L. R also has a physical mode switch that changes its behaviour, which is used on Windows to toggle between XInput with analogue triggers and DirectInput with digital triggers like the Switch expects. So it may be worth us trying to focus on getting digital trigger mode specifically working on the original and later firmware models.
(And there is also the Apple MFi centric C.T.R.L. I that I don't have any experience with, which is another story.)