I got the idea from someone saying the best way is to hide the needle in a stack of needles, not in a haystack.
I am considering writing a little app to accompany my Keepass installation. The app would create X (1024?) .kdbx files with random encrypted data of various sizes. They would have random 3 character names. I can then delete any of those files and save my "live" database in its stead. After I am done with my Keepass session, the app would then need to 'reset' all time related meta-data (date and time last edited, for example) of all 1024? to avoid my "live' .kdbx file to stand out of the stack of needles.
The idea is to discourage a would-be password brute force attack.
Other than having to remember a 3 letter word, what down sides does this have?