On the initial idea, with a faster timer: It runs codetools, so there is potentially a lot of computing, and while many systems are fast enough, that is not the only issue. For examples users on a Laptop will experience the extra drain on the battery...
First of all, there are several updates triggers. For which do you wish the increased speed.
1) When you are typing inside a block of code?
2) When you switch tabs
3) Other focus events
....
2 (and 3) can maybe bypass the timer, and directly use an "OnIdle" or even an ASync event.
As for 1, well that could be further cut down.
E.g. maybe it can cheaply (though probably not trivial) be detected, if the caret just moved to a diff procedure, which could trigger an update.
I don't know if any other edit or user-input really needs faster updates....