I see the exact same thing in dev envs, and even more so in ops/sysadmin. Cheaper unskilled labour going through old fashion processes without questioning and never trying to improve.
I'm not so sure. I think its binary.
I think there's always a touch, a qwan, assumed knowledge, skill & craft, or something that's not captured in the SOP.
The master baker in the shop next door made the most delicious brioches. Left to start her own catering company. Whereas her trained replacements, using the same recipe, ingredients, and gear, just made adequate dinner rolls.
I spent years perfecting my sunday morning pancakes. Big and fluffy. While best ingredients help, there's still a touch to make them just right. I can't even delegate flipping the pancakes to untrained family members.
I've seen this with other trades too.
You and me, we're too close to our work (tech) to fully understand the value add we bring to our work. But you miss it when it's gone.
Maybe this is why the master / apprentice setup seems to work well for knowledge transfer.
A good cook can repeatedly make a really good meal (CMM 2) but not necessarily being able to explain how and why.
A Chef can setup processes and direct any cook to repeatedly prepare really good meal (CMM 4).
A Master will improve existing recipes and invent new ones, will invent new processes to make better meal and make the kitchen work more efficiently etc... CMM 5.
Continuing with your pancake example: the way I make bread in summer is different than in winter. In summer, I expect the dough to rise faster. If it's a really humid or dry day, I'll do things differently. If the flour isn't the same as last time, I can compensate for that, etc...
Process either requires tight feedback to work well, or all variables have to be minimized.