If I was starting a config for a PC program, I'd start with a Mouse2 Reference Card:
and start planning what commands the program uses the most frequently and place those around the center of the card.
AutoHotKey can be used to expand Ctrl/Alt/Key outputs issued from the Quadstick into more text for the ACAD command line. A lot of ACAD commands are single letters anyway.
Looking at an ACAD keyboard commands list:
You could map a lot of those commands into a quadstick spreadsheet.
With a three hole mouthpiece, there are six hole combinations,
single hole, or pair of holes, or all three holes, times sip vs puff
times hard vs soft, for four basic signals per hole, gives 24 discrete
signals. If you combine that with short vs long (tap/delay_on), that
goes up to 48, theoretically,
That ACAD keyboard card has 34 (I think) commands.
The problem I would have is to remember all that. Probably it would be best to pick the most frequently used dozen or so commands to map to the mouthpiece, then use voice for the rest, or special mode sheets for specific situations.
Regarding the mouse sensitivity, play around with the
three response curves (0=linear, 1=mixed, 2=parabolic). Parabolic can allow you to slow down the response with small deflections and speed it up for larger ones. Windows and ACAD also have their own mouse pointer controls, and they are probably assuming a linear response for the raw mouse input.