If it's a simple SaaS by all means go for it. I really like the idea of being able to toggle things I like/don't like. But most of the times I become a "second-rate" citizen in the eyes of devs when I'm on a lesser-used subset of features.
Example is this service I'm using to manage my small company's finance; because I refuse to toggle on a feature that makes life easier for most people (but not mine), getting support for bugs has been very difficult.
Finding the combinations that result in something broken (through some unexpected interaction of features) would be impossible via QA. I guess you could keep a list of the more popular combination of settings and test those. More likely it means you'll let the customers do the QA for you. The customers will not like that.
If you've ever maintained a system that uses developer feature flagging, the cost is large and typically this is for feature flags that should only exist for a matter of weeks or less.