Having components with lifecycle methods called at known times by the framework is a perfectly straightforward mental model. It's worked just fine since the beginning of time. iOS still uses it.
I remember investing hours (and days and weeks) migrating old code to the "new way" or trying to get some simple thing "working with hooks." Other than being able to share in the authors' feeling of smugness over the unnecessarily-convoluted mental model when we finally got it all working, I genuinely can't recall any value we got out of the whole investment.
Android, too.
In the end, hooks have greatly simplified things for me.
So are the users wrong, or did you screw up?
If you're not properly tearing down what you're doing in an effect, you're just making room for bugs.
These have always been true of useEffect.
When you have to rewrite the documentation to basically tell the world "you're holding it wrong" then it says a lot about the thought that has (not) gone into designing the feature.
And that's why I think I'm done with React for now. It just does not spark joy.
If anyone reads this and I am wrong please comment, but from what I can see that's the only solution.