Well, for all you guys with a LOT more finds than we have logged, it may be too expensive from a payload perspective to include your FOUNDs all of the time. Especially if you log from GSAK as a rule. If you wish to keep those FOUND caches updated even after you've found em you can always filter em and click "Update Caches" which will capture both status and recent logs. I have found a few occasions when I need current data on My_Finds loaded so that I can cache with a group or my BFF that haven't logged them yet.
I see no benefit trying to keep multiple DBs updated. For example, isolating a current My_Finds filter is one-click activity in the latest version of GSAK. V8 has changed everything. When I need a separate DB I simply generate one on the fly with a couple clicks. It's much easier to maintain one DB, and performance is quite acceptable with a 25,000 row DB. And, that is on my "Sanford and Son" old laptop PC (not a 486, but close)
For you guys with lots of hides, again, it's no big deal to isolate them, and keep those logs fresh with a click, if you don't want to have a separate PQ for Owned by, or include Owned by Me in your scheduled geographic PQ's.
Whichever way you choose, a macro may reduce a few clicks, but so far, at my level and caching intensity (antithesis of Texas Writer), a macro doesn't do much for me in this regard. My macros tend to be reporting, analysis, conversion, and presentation utilities. Not so much for automation right now.
Why am I all sweatty and late? Umm...