For loaders which load user-data, it might make sense to reload periodically.
Expiration will not cover this as entries should expire after X hours but that means after load all it expires i.e. 0:00 but the entries are not loaded immediately but on demand which mean they are expiring at different times.
If entries within the DB are updated K1 might be loaded before and K2 after that and could be inconsistent from an application perspective.
Another aspect is to schedule the refresh at one time, i.e. after the expected DB update and at a time where low throughput is expected.