I take it the smiley means you know this, but to be clear, that’s not the kind of rewrite we’re talking about. Fossil is against providing multiple/alternate sequences of commits that can represent the same timeline. Breaking the Merkle tree isn’t even in consideration (because a determined adversary can just as easily break Fossil). The discussion is really over workflows and perceptions, and has very little to do with the technicalities of preserving history.
Both bitcoin and git use merkle trees to prevent (unwanted) history rewrites :)