Then develompen velocity goes down the drain :/ (which grows exponentially more unmanageable the more developers/applications you add to the mix)

In my opinion what you suggest would be a good solution... But try to pass that by mos. Manager for which (in most companies) we are already late to compleate the newly received feature/requirement

But "development velocity" is velocity at doing things well, not at all the same kind of velocity as the velocity of a truck flying out of a sharp turn because the driver likes being fast and dislikes braking.

A sound architecture (admittedly unlikely) would help the kind of incompetent organization you allude to to maintain order and fail later.