> After 10 years experience gained in the field would vastly surpass any differences in fundamentals in my experience.

Yes and no.

If your colleagues are Peter Norvig and Richard Gabriel and you are programming editors and compilers, then you will probably get a Masters (and more useful than most) in CS simply by talking to them on a daily basis and coding your ass off inside a codebase that they're working on, too.

The problem is that very few companies have people that good or problems that challenging. If you go to work for an insurance company after a bootcamp, are you going to learn how to build a compiler? (And, call that esoteric and scoff if you will, but I have built a "compiler" several times in my career because it was the best way to transition from a legacy system.)

Now, to be fair, maybe nobody cares. If you're rewriting a CRUD app for the umpteenth time in "YetAnotherFrameworkItsBetterThisTimeWePromiseHaHaHa", then it's not going to matter. Knowledge about the current system and all its tendrils is far more valuable than pedantic graph theory.

However, that's local system knowledge and has no value outside your current company. The only knowledge that has value to your next employer is domain knowledge--at that includes your baseline CS and programming skill.