Can you provide a link to the post that describes how Satoshi could create a fork if he were to spend the coins in block 0.
All that was saying is that if there were a release of the client where that bug was fixed, then the first transaction that spends from block 0 would be accepted by some nodes (those running the latest software with that fix) and it would be rejected by others (those that hadn't obtained the update).
Thus the blockchain will split, with some mining capacity happily carrying on with the the fork that includes the "block 0 spend transactions", while others are mining a different longest chain which has no "block 0 spend transactions". Which of the two ends up winning depends on if enough exchanges, merchants and individuals will accept the coins the miners earned from mining on the fork. If not, miners finding that their coins are worthless abandon the new fork (and the coins they thought they earned) and stick with the version of the client from before the change was made.
Thus that is a hard-fork feature.
These hard-fork features aren't impossible to roll out, just that they require an economic majority to accept them otherwise you can end up with a forked blockchain. To avoid this, the Bitcoin.org developers generally don't propose any hard-fork changes unless there is a damned good reason to do so (and a near certainty that the economic majority will accept the change). So that Satoshi can spend his 50 BTC (
plus whatever else has been sent to that address since [Edited: Thanks Foxpup]) is not a good enough reason to implement a hard fork. And "fixing" it will potentially introduce the risk of this fork occurring, so it won't be fixed for now and this behavior is essentially now part of the protocol.
It isn't even something on the "wishlist":
-
http://en.bitcoin.it/wiki/Hardfork_Wishlist