You could add a task, where you start/stop your proxy cluster with databricks cli.

another consideration:
Do you even need the cluster if you're running a job? I assume that the job refers to code in a Git folder? Instead of the Git approach, you could deploy the code artifacts with asset bundles. That way, when you start a job, you don't need a Git proxy cluster