The caching thing is a red herring. Dude thinks you've got some kind of old/slow computer. You don't. No program should take 55 seconds to load on a fairly modern system.

The only way the caching thing that he describes would be true, is if somehow your disk drives were super slow. Slower than tar, slower than they should be on any modern system. Like... A SATA drive that is running in compatibility mode because it doesn't have a device driver loaded or it wasn't detected by the BIOS correctly or something. If that were the case, you'd notice performance problems across the board, not just in that one application. (do you?)

The only times I have ever had a program do the "slow startup" thing, it was because that program had been used to open a file on the network or on a removable drive somewhere in the past, and now that old file was in the program's list of "recently opened files", but now that network share or that removable drive is gone, so now the program tries to start up but it sits and hangs and waits for 30 seconds on each instance because it is timing out on the network or disk query for that (now gone) location.

Try: Clean out the list of recently-opened-files in that program.

Or, look for some other thing that the program might want to be opening (some kind of file or folder or library or network printer or web site or something) that is now gone/deleted/dead/disconnected/slow, that might be causing it.