Because all those features are native to Django, you don't need to combine libraries by different teams with different code designs, together with code glue. You don't get the rough seams at the edge of one library's code with another. With Django, everything works together with everything else, seamlessly.

But the other side of that coin is that realistically you have to work Django's way even when Django's way is poor by modern standards or you'll be trying to swim upstream forever. The historical baggage and limited support for modern language features and programming styles are among the reasons that adopting a lighter web framework and then mixing and matching best-in-class libraries has been an increasingly popular choice. Most of the problems you mentioned with this strategy turn out to be great big nothingburgers most of the time.

I feel obliged to point out here that this debate isn't really specific to Django or to Python web frameworks. The above are all classic pros and cons of a heavyweight framework vs a collection of lightweight libraries. With the framework you get batteries included and you get consistency but you also get lock-in and usually - if it lasts long enough - stagnation. With libraries you get full flexibility and can be as bleeding edge as you want but you're on the hook for making everything play nicely together. Either way you make your bed but then you have to lie in it.