That wouldn't be so bad, forking is where innovation can happen. The really bad part is when it would have the "Webkit" label in the user agent string, claim complete compatibility, claim they are using the most popular rendering engine, but being broken or incompatible in some fundamental way.
That doesn't make much sense, if MS creates their messed up own fork of Webkit, how does that hurt you?
Your stuff will still break in IE.
Fragmentation.
It would still be called WebKit, but it would be somewhat compatible with other implementations of WebKit.
Remember Microsoft's Java.
How would it be any worse than it is today?
If Microsoft starts using WebKit, they'll find a way to fragment it and make their implementation of WebKit incompatible and unmergeable with the rest of the crowd.
No. Please, Microsoft, stay away from the projects I depend on.