This is starting to sound to me like it might be an X-Y Problem.
Please describe in more detail how you envision this client is going to be used, the sequence of events surrounding its usage, and what you think the “lifespan” of this client is going to be.
Keep in mind that code you write does not execute outside the context of a request-response cycle. There is no way within core Django to create a persistent process that is going to continue to execute after a view returns a response. If you’re thinking of doing anything like this, you’re going to need to set this up as an external task, using something like Celery to manage those tasks.