The low level problem here is your team doesn’t realize that every word of code means something.
You need to get past the idea that code has to be there to do a thing and get to the place where you expect every bit of code to explain something.
“Why is there a useMemo here”... if your team can’t explain that, then “changes requested”.
I've seen a lot of cases in the wild where useMemo was used to wrap closures, "for performance reasons", but that's obviously more wasteful than just using the closure by itself. I think a lot of people don't realize that.
That said, you're correct in that this should be the exception and not the rule. It's pointless to do this for a component that returns a single element, as the virtual DOM reconciliation will be much faster than the memoization + props comparison.
I've created a CodePen to illustrate: https://codepen.io/RussianCow/pen/xxbERLL
Open the console and watch as the "render child" message is logged once per second, showing that the child is re-rendered every time the parent is.
My main complaint with hooks is people seem to think they always need them. I've seem components where every single piece of data, no matter how trivial, is slapped into a useMemo(). It becomes a lot of mental overhead to trace through them all, especially confirming the useMemos have the correct dependencies specified. Especially when the vast majority of the time, useMemo just isn't needed.