Personally I do not mind a huge symbols base. As long as the core is clearly outlined and well documented.
Which is not the case because there is no clear border between "the base" functions and all syntactic sugar or utilities that are around. Or rather, the clear base subset is there but it can't be filtered from user perspective. Experience taught me to not touch those utilities/sugar when developing code for others. And in this context an ability to extract the core functionality and learn 'what is going on' is very important.
I deliberately steer clear of giving specific examples to not put anyone from developers on spot just because I recently use certain functionalities rather than others.
Summing up, I agree with your point but not with the suggested solution as it would require too many changes.
What I think would help are semi official developers' notes about core frameworks. While documentation should be clear, user friendly and readable for newbies, developers need clear details in technical language.
I'm not sure about format/distribution for such notes but I know they would help. Especially in case of core features that have no documentation at all. PacletManager
is a distinctive example, why something that fundamental to Mathematica needs to be learned by reading the code?