Odin is more dangerous than CWM... I've never seen CWM brick a phone unless the underlying kernel was seriously broken (which it is in this case) and in such cases the kernel should be avoided at all costs.
I'm serious - I would strongly advise NOT running any kernel derived from this leak AT ALL. If a CWM wipe can damage the eMMc, then so can similar operations such as deleting a large file.
Right now a number of the ERDs are speculating that it's due to Samsung enabling MMC_CAP_ERASE (a variant of the TRIM command) in their MMC drivers - our eMMC chip might not like receiving erase commands. A full CWM wipe is a classic example of a large batch erase, but deleting a large file will cause the same kind of commands to get sent out, as will a data wipe in stock recovery.
Here is why I liked mobile ODIN better:
1. It doesn't flash bootloaders. So all the risk related to the desktop ODIN is gone. And it can root the phone while you are flashing.
2. ODIN is similar to what Samsung does internally for testing. So, it is tested and verified by Samsung to be working in most cases. On the contrary, custom kernels packed with CWM doesn't go through this. And the fate your phone is dependent upon one developer's thorough testing (or not) and understanding of what changed in the latest code.
3. Samsung can intentionally or unintenionally break the code for CWM support. As far as Samsung concerns, it is a non-issue because it does not officially support CWM in the first place. So, the only way to find out if the kernel works or not is by some unfortunate sol bricking his phone. Like this example. There is simply no way to prevent this from ever happening.