But frameworks were never made for solving that problem. Partial content download is a nice addon, but not a goal. The goal of any framework is providing of code structure with some concepts (like MVC) to ease development. Without that it would be a library.
MVC doesn't require a framework or a library, it's a concept. It just requires models, views and controllers. And it's also pretty much not needed at all in the front end unless you're doing logic solely in the front end (which not many sites do at all). It's usually used to grab data via JSON.
You can write MVC app yourself, but that's like development of a bicycle: it may be ok if that is your goal, but if you need to make app fast and avoid stupid bugs - it's more effective to use frameworks as they are well designed and tested. Neglecting to use frameworks is like preferring assembler.
That assumes there's boilerplate in a model, a controller or a view. Why is there boiler plate there? There shouldn't be. Writing a modern MVC app is simple. Writing an Angular app actually forces you to write Angular code, not MVC code. Same with React. Etc.