It doesn't have to do with being on the correct chain. That was simply a big mint and clients are rejecting it (not necessarily for being a big mint, per se). If that mint stays in the chain it will get rejected with the current clients. That's why you got the forks. So what do you do, take the transaction out of the chain?
That's a rhetorical question. No, you don't do that because you have to rewind the chain and really fork it.
Do you give the block a specific pass in the code?
That's also a rhetorical question. No, you don't do that because that doesn't really fix the underlying problem and a future issue like this is inevitable.
It's a valid block. Cryptsy didn't do anything wrong. It's the clients that are in error. They are rejecting perfectly good blocks. The correct answer is to fix the clients so they sync right up and people can stake as many coins as they have without worrying about forking the chain.
That's what I am here to do.
Other problematic blocks according to your clients: 19674, 20568
These types of blocks fragment the network and will cause forks sooner or later. They also drive away users.