Comment: what’s been moved from this thread is about unexpected firing of “system started”, in turn caused by refreshing of rules files.
Note that any in-flight rule file refresh will lead to the “known” effect of a delayed first-time rule run, there is a link to the symptoms here but not the root cause.