Askama (there is also tera, which I haven't used) implements jinja2 templates, so that part looks exactly like Django. I rewrote one of my Django apps in Rust, the code related to templates is identical, with benefit of type verification. Every web framework out there can do routing, and you could easily add whatever syntax/conventions you want to have. I wouldn't design it the way Django does it today, but you easily could do that.
If you want Django as it is today, the only missing part is ORM and migrations.
The only working option here is Diesel (which I am not big fan of, at least using it as it is now).
For migrations there is barrel, so this probably could be done as well fairly easily.
However there are few things that changed since Django was created, so exact copy is not the ideal option.
- People use Angular/React/Vue and generally handle frontend with js tools. I don't do frontend work so I am not sure how would that affect design of web framework, but it probably does.
- Async is far more popular, and even Django has plans for that. However Rust async doesn't really exist atm (99.99% of library authors don't care about that and won't for near future).
- Django doesn't care about deployment story, leaving many things to docker/uwsgi/nginx and others.
I don't think new framework today could leave it that way.
Also Django relies on Python being interpreted language. Your authentication backend is defined as class name in configuration. You woudn't want that in Rust.
And I run manage.py shell very often to test code or check/fix db issue. I miss that a lot with Rust.