The feature isn't obscure... it's a correctness feature in btrfs, and hardware support elsewhere.
Basically btrfs needs to know that the checksum is right because it will check the checksum when the page is read from disk next, so if it can't do that it WILL report spurious errors and potentially loose data depending on how your app or you react.