If the version is not covered by the HMAC, you may be subject to rollback attacks. Compare the SSLv2 and v3 protocols to see what was done to address this.
Really, it's very easy to make a mistake.
Really, it's very easy to make a mistake.
Also, unlike session cookies, SSLv2 never had a hard expiration date after which it could be unconditionally rejected.
However, I did just realize that for perfect security, there must be a service disruption on change of version. Otherwise you may be upgrading an attacker's forged v1 cookie to v2, if they submit a request before the v1 expiration.
http://rdist.root.org/2009/08/06/google-tech-talk-on-common-...
Your last paragraph shows you now have better understanding of this.