That's pretty wacky... sounds like a work around but glad you got it sorted. I'd assume they'll adjust those values once some polish is put in and it's something that's being sold to the general public anyways.
The reason is because of the clock rate on the controller. MW and CF are running at 8Mhz but Tau is running at 12Mhz which makes things a little different. Here's the explanation from the git pull request:
I've done some outdoor tests with Quanton. I used 1000Hz MPU rate and set the PWM range 1500..3000 to produce 125..250µs signal range (multiplied by 12, because of the 12MHz time base). The copter was measured and set up by auto tune and the PIDs were high (higher than usually). It was very windy but the copter was still very good to control. The Flightmode Level was like nailed.
I'm still getting my head around all the different frequencies involved (rate of the processor, rate of the various timers, rate of communications between the FC and ESC, PWM rate of the ESC to control the motor, rate of the signals from the RX to the FC....)
And yes oneshot on Tau is still very experimental which is one of the reasons why it has to be enabled through the uavobjects browser and hasn't been added to the GCS GUI yet. It's kind of tricky to detect the situations when it can't be used and there's still some debate about how to add it to the GUI. (It has to do with the internal timers used for generating PWM and the variations between different boards that Tau supports.)