I haven't touched Django in the last 6-8 years, but I've been able to solve first few problems just with basic common sense and SQL knowledge.
Are those problems really about Django the framework and not about data modeling in relational databases?
Are those problems really about Django the framework and not about data modeling in relational databases?
These problems I think are more to do with inertia and not having best practices in mind. It's easy to do CharField and not thing about TextField.
Plus over time requirements change, so when a model was created maybe the kwargs were perfectly valid - but over time as refactors occurred tech debt crept in.
In Node environment, I think that I would be able to come up with an ESLint plugin. Doesn't Python ecosystem have something similar?
This is why linters let you ignore lines/files.