Genuine question about your git-driven comment.
From my hands-on engineering POV I often set this maybe not as a hard requirement but definitely a goal, and the places where it's not possible I find a little painful.
In your case where is it becoming something that doesn't make sense for you?
Let me add my 2 cents on this.
The most unconfortable place for GitOps is when you need to keep in sync values that user could define via product UI/cli. For example you change theme color in UI, but you have the same settings you can define in Helm chart inside a git repo. So that brings you to dilema, where and how to store dynamic settings (this could be just inside K8s api change via UI/cli) but changing all of this using GitOps way (UI/CLI-> git commit -> wait reconcile) breaks the comfortable user expierence.
Same things with dynamic changes just for test something, you need or commit temp change and commit back old value again or just pause controller from updating during your tests.
But the bright side of this is the fact that your configuration completly traceble and you have whole IaC backup for your infra in unrbreakable place (git).
For now we fully perform all updates and all configuration with Flux and this was a good decision I can retrospect.