Hehe. USB type C client is not actually that hard to make.
To convert an existing USB 2.0 device to USB Type-C, the designer can short the two CC pins, add one Pull-Down resistor and route the USB D+/D- signals to both positions on the USB Type-C receptacle. No other changes are required. The device waits for Vbus to be valid, enables its D+ Pull-Up resistor (for a Full Speed or High Speed product), chirps (if a High Speed device) and USB enumeration occurs as normal.
So basically one resistor and a socket is all it takes to convert USB 2.0 device to USB-C. Breakout board will be quite cheap to make.
500mA only though, so that 2.5Ah battery will charge in years. Years, Carl! And it has to be the last device in the chain.
And lo! Someone even makes them already.
As for the combo device - USB part can go to deep sleep when not connected. Won't risk to say "turned off - you can put a diode into +5V between the parts so it can power the BT+controller part but not vice versa" - not sure both parts survive. But kitprog seems to fare well with this setup.
USB-C devkit is
a bit pricey though. Damn you, new technologies! Also PSoC creator doesn't support it yet, though they promise it. In December 2015, no less
![Smile :)](./images/smilies/icon_e_smile.gif)
There also bound to be other vendors who make USB-C MCUs/SoCs. Otherwise how all those smartphones have USB-C ports?