Can Toggle Feature Flags totally replace the Hotfix Release branch process?

1. Currently, when seeing bugs in Production, we first make Change in Develop branch which contains ongoing changes and test it.

2. Then we also merge fixes into Release Branch or create Hotfix branch. Merges and cherrypicking are prone to errors, or people forgetting to place in code properly.

3. Another reason we have release branch, is since some modules are not ready and don't want them showing in Production.

We are thinking of instead using Toggle Feature Flags, to replace the Release-hotfix branches, allowing us to deploy daily. Leaving us with only a Develop and Master Product branch. Would this strategy make sense?

https://launchdarkly.com/blog/what-are-feature-flags/

https://martinfowler.com/articles/feature-toggles.html

Current Git Strategy similar to this:

https://nvie.com/posts/a-successful-git-branching-model/

When using a git strategy similar to gitflow, can feature flags totally replace the Hotfix Release branch process?

When seeing bugs in production, we first make the change in the develop branch and test it. Then, we also merge fixes into the release branch or create a hotfix branch. Merges and cherrypicking are prone to errors, or people forgetting to place in code properly.

We have a release branch since some modules are not ready and we don't want them showing in production.

We are thinking of trying feature flags to replace the release and hotfix branches, allowing us to deploy daily. Leaving us with only a develop and master branch. Would this strategy make sense?