I've come to some new realizations that no one has mentioned in here as to why the code is locked actually. It makes a whole lot more sense when you look at it this way too. This was information that was given at another website for a different app that clarified completely why it's locked.
Basically their explanation was that if they unlock it, it will be changed within the app by the users. This totally negates any possibility of easily updating it when Bootstrap itself is updated and needs to be updated in the app (such as when we went from 3.3.7 to 4.0). It would be almost impossible actually, because everyone would have altered the default files that the app is using as it's base and those are the files that would be updated. What does that mean to us?
Means we would lose every single bit of custom coding we added/changed/removed/etc. to the default files and we'd have to start over.
@Martin and anyone else that's tried to defend this setup. If you had said that to us in the beginning, I bet that we would not have had all these conversations about unlocking it all to start with.
But ... We should still have the ability to duplicate all parts of a component and edit them without touching the default code itself, same as we do for the CSS. Has to be a way to do this I'm thinking, but ... I can most definitely say I agree completely with the above information about why it's locked, and it does make much more sense to me now.