You don’t want “Django” to do or manage that.
You want to use something like Celery, or even a worker task in channels. Both options do give you access to the database using the ORM.
You want to consider the complete life-cycle of the process - once it’s started, how long is it going to run? What is going to monitor the status of that process - possibly restarting it if it should fail for some reason? How many instances of these are going to be running? Do you have a way of limiting that number of instances?
This type of “process management” is one of those things that is an extremely bad fit for your Django wsgi process. Do it external to Django.
That would be a mistaken conclusion. These tools are generally used to run tasks that will exist beyond the lifespan of the view that initiated them. It makes no assumptions regarding the timing of the tasks themselves.