The following issue occurred in Microsoft's 4.7 .NET framework update.
"The internal implementation of System.Web.Caching.Cache uses Coordinated Universal Time (UTC) time-stamp for absolute expiration. But this particular Cache.Insert (string, object, CacheDependecy, DateTime, TimeSpan) Insert overload method does not make sure whether the expiration time is converted to UTC. Therefore, expiration for items that are inserted into the Cache object by using this overload will occur earlier or later than expected, depending on the computer time zone difference from Greenwich Mean Time (GMT)."
This meant that customers using Cache.Insert could see a higher frequency of database calls since the caching was not used.
Please see the following blog from Quan Mai for a code workaround and for an official fix from Episerver.
You may resolve this issue by updating the CMS Core to 10.10.2 or higher.