There are plenty of good reasons to "bork its update process", for example if you work in enterprise and have a change management process for browser updates. Or if Chrome introduced a feature you don't like (like Lion fullscreen). Or if you prefer to use your OS's package management system for browser updates.
It's not so much a matter of Chrome's update process as your update process. If that's "I want the newest version as soon as it comes out, all the time", then great, but there's no guarantee that's true. That's the exact reason Firefox is doing its whole ESR thing.
And since you're bringing software updates into this, even though an optimal strategy will target both problems independently: one can't force users to restart without a lot of pain, as long as there isn't true session checkpointing.
[0] Thialfi: http://research.google.com/pubs/archive/37474.pdf
Well sure, you'd get the cert revocation updates, but you wouldn't get security fixes, which seems equally Bad. Why wouldn't you just let Chrome do what Chrome does? What would you gain by actively borking its update process?