My initial reaction is that there seems to be much bigger issues with the way your company is structured. The words you're using ("lone", "carved", "straining on the edge") suggest a stressful situation where each individual carries their own weight... If that's the case, I can certainly see why you'd be upset by someone else impeding your ability to work. I wouldn't last long in an environment like that, either pushing it to be more collaborative, or just leaving.
I can't imagine any coding that isn't improved by adding collaboration (a great starting point is code reviews... make PRs early and get opinions on rough-cuts). If you don't have this in your current environment, I highly encourage trying to kickstart it... you're really missing out on a great way to remove stress, improve quality, and have more fun.
The inherent technical complexity of the components is such that sometimes a feature needs days of coding - thus the 'more locksmith, less of a ballgame' analogue. I should have perhaps pulled some other analogue.
My coding has very little to with sport-like activity and is more like the task of a lone clocksmith (although we have a team, individuals have quite large chunks of codebase carved for themselves).
For some problems I am straining on the edge of my working memory capacity.
The problem with the distraction avoidance is that it demands mental resources. If there is some benefit in training working in a stresfull environment there could be a sound proof room for such a purpose where employees could go for a limited time to train. The inverse of large open office/small quiet room pattern.
At first level there could be just white noise in the room. Once that is mastered as an added stimulus the feet could be placed in a bucket of icewater. At the next level the room is filled with monkeys. Etc.