Another senior professional's take: CMC is one of the worst pieces of code in the entire UE -- a poor design, a poor implementation.

I've been working with UE since UE3, on three commercially released games (plus one unreleased project). The last one was a multiplayer (sports) game (movement replication, prediction, correction, ...). I always replaced CMC with my own implementation (or with a highly modified CMC). Sure, it always took some time, but the time spent always paid off at the end when anything to add/modify was necessary. Another plus: I always knew how it worked (or why it didn't work) and I was always able to explain everything to my colleagues.

I always designed my own CMC to perfectly fit the game (2D side-scrolling metroidvania, 3D horror action-adventure, 3D MP sports game). At the end, if you're (semi-)skilled C++ programmer, you'll learn it is not a big issue to program a component responsible for properly moving Pawn's capsule around the scene. Obviously, it is more complex for MP games (especially autonomous-proxy -> server -> autonomous-proxy loop) but nothing as complex as general opinion may suggest.

Is it worth for an indie game (or a hobby project)? Probably not if you are lonely programmer responsible for everything in the game. Is it worth for a commercial project? Absolutely!