The alternative is to not have (most of them) at all. The reality is that 99.5% of users have perhaps 10 or 20 actual usecases/requrements. - You named a few o

The alternative is to not have (most of them) at all. The reality is that 99.5% of users have perhaps 10 or 20 actual usecases/requrements. - You named a few of the most prominent ones. These need to be supported (e.g. with flags) and documented properly. Everything else is excess can be removed. The problem with this is: You need to find out what users want to do. But many software projects are just too lazy and push all the effort downstream.