Process stucked at the start after redeployment

Deployment aware is difficult.
The individual engine will not work correctly after a restart, as it will not be aware of the fact that it has any processes deployed to it. This is why you are able to repair the problem by pushing any small change. The deployment is then registered to that engine. See also Deployment-Aware Job Executor
and also
The Job Executor | docs.camunda.org