We've moved the other regular hints to standard balloons now as well, which should, as a side effect, make those constant forth and back with resilient software that doesn't accept someone is not accepting their changes less desktop cluttering.
Thanks for the hint that many users don't really want to know about these things as well - I went ahead and added an option to either show them or not to give the user the choice here. The point of it was to show some progress while processes are scanned on startup, so we decided to have it enabled by default.

Caching between seasons works fine now as well, making a rescan only necessary if either the database has been updated, or a file has been changed.

As for choosing between the two methods, we decided that it might be best to automatically switch depending on the memory a machine has available.

We'll be looking at possible improvements to the low-mem method again tomorrow, but after that, we should have a new TeaTimer for testing available here (and I hope the new verbose mode has enough output to even find that permanent stall)