in a way that is specific to the codebase
Well I would say this is not at all specific to the codebase - as I said above, it applies to basically all code bases that use mutexes, since poisoning is so rarely relevant.
These two statements are kind of strange to me:
Talking about a method returning a Result like it’s a big deal must be some sort of splitting-hairs maxxing.
and
And btw, as it just happens, such traits actually already exist, in a crate that is well-known to the ecosystem.
If this is such a small deal, then using an external dependency is a terrible solution. That's like the whole left-pad situation, a dependency to solve an extremely small problem, but something that affects many, many code bases. That's exactly the use case that the standard library should cover, exactly so that you don't need to use an external dependency for such a trivial thing!
And yea you could say "duh just write the extension trait in your utils module" but this is just not acknowledging the problem at all and just sidestepping it. That's not helping anyone.