What if it never gets better? How can you rely on third party if that can make C2 look bad if they do something wrong?
Well, it already is better - check yourself by running Canary. In time that will make beta, which will then make stable. Given all browser makers have been putting in a great deal of development resources in to browsers for the past few years and Chrome and Firefox in particular pushing very aggressive 6-week release cycles, I find it very difficult to take seriously the idea that anything will stay the same forever, particularly when Google say they are aware of the issue and are working to make v-sync scheduling flawless.
Modern software development without relying on third parties is practically impossible. For example some users suggest we use Haxe instead, which is just a different third party and we could equally be hosed by problems with Haxe. (I also doubt it has as much testing and development resources going in to it as Chrome does.) Imagine if we wrote an engine depending on XNA - Microsoft ended up dropping support for that. Or Silverlight - the same just happened (they officially announced recently Edge won't support Silverlight!) All platforms have their quirks and risks. Chrome's v-sync scheduling is a bug - it's been a problem for a while, but it's just a bug like any other - and as far as I can tell it's already fixed in Canary, where according to sbperftest on my dev machine the maximum jank is just 0.1ms off v-sync.