From HG's own documentation (https://www.mercurial-scm.org/wiki/ChangesetEvolution):
>While well on the way, the full implementation of the changeset evolution concept is still in progress.
HG's entire system requires far more investment in the tool than git will ever ask of you. And you probably don't need the feature in the first place. I consider changeset evolution a nifty feature, but it's also a devop smell in my book.
Evolution requires no effort whatsoever to maintain.
As far as smells go, its whole purpose is to make editing history less "smelly" than git's rebase -i followed by force push.
You are not a full blown development team, and beta software works for many people. That doesn't mean it's ready for prime time.