This could cause them to reconsider that decision. In fact I'd go so far as to say this should cause them to reconsider their decision. Perhaps they'll come to the same one in the end, but this is a radical landscape change and it is appropriate for the standards committee to react to that and not just passively say "Oh well, the standard is written in stone, so sad."
If there's any consistent theme to the history of web standards, it's that all the successful standards start as someone's proprietary extension that eventually becomes a de facto standard before being codified by the standards committee. Standards that start in the committee rarely gain traction.
Safari and Chrome both use WebKit but they use completely different code to implement <video>; Safari uses QuickTime and Chrome uses ffmpeg.
The argument used by both of them is just convenient excuse. What do you expect of them? To tell you what is in the above paragraph?