Is there any actual hope this is going to be addressed or removed at any point in the near future? Other platforms are actively combatting this whilst Zwift sit on their hands. WTRL have hinted this is being looked at, but who knows if there is any accuracy to what they say.
Obviously it would be super simple to just change the 3s timeout to 1s and sticky watts would not exist anymore. However, this would cause problems with low cadence (< 60 rpm). Changing the timeout to 2s would nerf sticky watts and would still allow rpm > 40 and could work as a quick fix.
An optimal solution would be to have the timeout dynamically adjusted based on cadence (higher timeout when doing lower rpm), but this can be potentially exploited (e.g. by using the smart trainer as cadence sensor and not the pm, etc.).
Training Peaks Virtual has released a. Update with this:
Exploitation of trainer hardware flaws like “microbursting” and “sticky watts” is now completely neutralized. If you try it in an event, you will now ride much slower – just like on a real bike – so it simply doesn’t make sense to try anymore.
They could always make the timeout depend on the cadence: otherwise change it to 1 second but make it 2 seconds if the cadence is below ~65 rpm or 3 seconds if below ~40 rpm. But clearly Zwift doesn’t want to fix this.