Tell that to MySpace, Friendster, etc. There is room for prove product disruption if the iteration adds significant value, or if the quality of service of the current leader drops off.
This seems an unfair leap. The most common cause of a checksum mis-match is going to be a partial download or something similar.
It's also not relevant to the current attack since the code was legitimately included in the official release and, as such, baked into the valid checksum results.
I think ZFS was just ahead. We considered btrfs many years ago to serve up VM's for ESX via NFS, but it just wasn't as performant unless you ran in async mode which jeopardized data integrity. ZFS let you introduce SSD-based ZIL and L2ARC caching which made performance totally fine in sync mode.
We're mostly NetApp AFF these days, but early on had close to a petabyte of ZFS-based storage power VM's on SuperMicro or Dell gear. Definitely was higher touch than NetApp but far less expensive.