Well, Kim Dotcom is still kicking it.
As for Ross, the evidence might have been circumstantial at best if his un-encrypted notebook wasn't grabbed.
In any event, Ross was running something somewhat more illicit than Megaupload. His opsec probably should have been commensurately better.
Even then, the FBI grabbed him with his laptop logged into the management interface for Silk Road... So he still would have been in some hot water.
(I'm not personally familiar with ZFS, but the ZFS docs, especially https://docs.oracle.com/cd/E26502_01/html/E29007/gkkih.html#... really creep me with regard to this. The last thing you'd want is blocks in your local encrypted copy of PHP source code to be compressed first. And so then you'd think you'd want encryption enabled on a pool, but from reading the docs it seems that feature merely makes the filesystems on that pool inherit that encryption option, instead of doing some sort of filesystem-blind block-level encryption, where there's any variance in the encryption of blocks, or any information that could be derived from locations of blocks. So I think the suggestion to encrypt on a directory-by-directory basis to limit your exposure is not a very good one. I'd recommend that you use a spinning hard drive, whole disk encryption of the sort we have today, take out the battery, and keep your foot by the power outlet.)