I guess i am just used to launch FARR search panel and type my program of file name without trying to remember which modifier for which folders or files is set.
That is all fine, but you have to take into consideration that FARR is not designed to search over large sets of files/folders, and forcing it to do so will just ruin the experience.
Also if you think about it, you'll have your search modifiers commited to muscle memory in no time, so that will become almost a non issue. I don't event think about what modifier is for what, just type and the right stuff happens.
I know it's a hassle having to deal with this, but when you think about it, you can probably get away with two or three different modifiers, depending on your setup. For example a separate modifier for network mounted drives, since they're slow by default. And one for large collections of files (ie music, documents or whatever)
Other thing you can do is try to narrow down the search, when defining search folders. For example I have a folder where I keep all my source code for projects, work and stuff, and it is a huge collection of files (19 GB, 150 000 files, over 29000 folders). However, when I want to launch something from there it is usually just the solution, or project file, and it is normally found 2 or 3 levels deep in the folder structure. So I have added file extension restritions to only include *.sln and *.csproj files, 4 levels deep into the folder structure, and now it is blazing fast - and it works awesome.
If you can't do that you can narrow the search by excluding files from folders, for example you will almost never want to launch a *.dll file, so add it to extension restriction (with a minus: -dll) so it will skip those files.
As I said, it depends on your setup.