There are separate render files for proxy mode vs original media mode. If you switch view modes, you will may see lots of "render dots" because the render files in that mode are not up to date.
Simply relaunching FCP should not cause current render files to become "stale" or show as render dots.
However this is sometimes observed. One possibility is a 3rd-party plugin applied to an adjustment layer or a 3rd-party generator. If those are incorrectly written so that upon initialization, they invoke some minor change, maybe re-read their last saved state and re-apply that, it could cause the Motion runtime engine to mark that as "uncached". In turn every clip (up to the entire timeline) covered by that adjustment layer could become uncached.
Something similar could happen if using a 3rd-party plugin such as Color Finale. I have never observed that, but a standard troubleshooting method is first exclude 3rd-party plugins.
My first suggestion is do tests to see if the behavior happens everytime or just some time, if it's related to a 3rd-party effect or generator, etc.
E.g, duplicate your timeline, open that duplicate, select all clips with CMD+A and delete all effects with Edit>Remove Effects. Render that timeline manually via CMD+A to select all clips and CTRL+R to render. It's obviously best to do tests like this with background rendering disabled, and start with all render cache files deleted.
If the copy of the timeline with no effects does not show the behavior, make another duplicate but leave all the effects. Then delete the effects on 1/2 of the timeline, then the other 1/2, then 1/4, then 1/8, etc. to narrow down which effect is causing the problem.
All your media and libraries should be on a disk volume formatted as APFS or Mac OS Extended Journaled, not on ExFAT. If your media or library is on a NAS device, please describe the details. In any of those cases it's possible the "last modified" info might not be implemented correctly and could fool FCP into thinking the cache files were out of date.