LUKS shouldn't be deciding what is or isn't a bit-flip. That should be detected at a lower level, such as the hard drive controller or a flash-based device's flash translation layer.
Mass storage devices have had issues with recoverable errors for as long as they've existed. Error correction codes have been used for decades to detect, and if possible correct, those errors. That is where minor "bit rot" needs to be detected and corrected.
In order for LUKS to perform error correction it would have to duplicate the error correction scheme that is (presumably) already in place. These schemes involve overhead -- for every X number of bytes of data, Y number of bytes of error detection and correction data must also be maintained. LUKS doesn't have space reserved for ECC overhead, so it isn't capable of correcting for errors.
1
Relevant: https://crypto.stackexchange.com/a/5593/4941
– user1686 – 2017-08-01T07:20:45.017