OBDII is not an emissions standard, it's a diagnotics standard. Hence the name OBD (On Board Diagnotstics). There are several protocol standards in OBDII like CAN, PWM, VPW, etc... The star mobile device does more than read diag codes. It also reads manufacturer specific codes, as does the dash hawk and most programmer/flashers. Manufacturers are free to implement their own pids, dtcs and protocols as long as they also implement the standard OBD functions. j1962 defines pinoutputs for pins 1 - 16 but leaves pins 8, 9, 12, and 13 unassigned and pin 1 implementation is left up to the manufacturer. Pins 6, 14, 3, and 11 were already for the can hi and low bus.
I completely believe that you are correct and current progarmmers will not work as each manufacturer implements this their own way. For example, on the old EECV fords using PWM one of the spare pins in the connector was required to be charged to 18 volts for ECU reprogramming. Chrysler may have changed theirs too. I'd be suprised if plain old DTC scanners stopped working, but I can't find any information where scanners say they support 2011's, I also can't find any information that excludes 2011's either (like new model numbers, firmware upgrades, cable changes, etc).
I had heard that the requirement for reprogramming over the OBDII port was going away, which would lock out aftermarket programmers. The aftermarket will find a way around this even if it means performing PCM swaps or sending out your PCM for reprogramming. I don't know if this has happened yet, I think as of 2010 they were supposed to be allowed to do this, but don't know if they have yet. Probably not because it's a big pain for the dealers to have to retool as well.
I don't do any work with OBDII hardware, but I have done work with OBDII software in the past. So while I am familiar with the software standards and communications protocols I am no expert with the hardware side.
Just my $.02