The term comes from this, and uncovers a bit of the futility about the so-called benefits of playing the imitation game:
https://www.steveglaveski.com/blog/the-curious-case-of-cargo...
The problem is that in the fast-paced corporate world, you either make your own startup (and usually fail at that), or you have to play the same game everyone else does. There's simply not enough time and resources to get ahead at everything. Unless you go for the smaller niche, ie. embracing agility. Of course, everyone and their mother is Agile (tm) these days too!
The key feature of cargo-culting is immitating another without understanding the why behind what they're doing.
Imitating is simply imitating. Many companies have gotten rich doing this.
Developers have a massive proclivity to follow something simply because others have. We're talking everything from best practices to design methodologies to whether or not to include a semicolon at the end of a line. There's a reason for this: writing software is very hard to measure and quantify. It's not a physical thing like a bridge or an automobile. When we hear about some new paradigm/framework/language/etc. espoused by some blue-checkmark-wielding developer who works at Google, we pay attention because...he works at Google, and seems like a trusted figure.
Not saying this is good or bad, it's just how it is.