Is there a way to combine helm with some other tool for k8s configuration management without conflicts?
Helm isn't made to be used this way.  If you'd prefer to use a static deployment, you're better off using a plain Kubernetes manifest.  Then, people changing the image field won't break your release.
You can easily convert it to one simply by running helm get manifest command
Helm is used to manage release versions.  I.e. every new release (and a docker image change definitely qualifies as one), you would push a change to your helm chart.
The other alternative you have is defining docker image as a value.  Then you can pass a command-line argument to replace the image tag with a new one and re-run helm from Jenkins any time you have a new deploy.
Example:
in values.yaml:
image: 
  repo: foo
  tag: bar

On command line when running helm:
helm upgrade --install my-app --set image.tag=newtag

Final, and least recommended way is to use a mutable tag (i.e. &quot;master&quot;) and set your ImagePullPolicy to Always.  This way, when you have a deploy, you just need to bounce all the pods in your deployment/daemonset/statefulset object.