Cron issues

We make an open source book publishing platform, that extends and transforms a WordPress multisite into a CMS for books. Each ‘site’ on the network is a book, and a given multisite can have hundreds or or more books/sites on it. We host several individual multisites/networks on a single AWS server. We use the Roots tools Trellis and Bedrock to manage application cofiguration and server provisioning, including managing a system cron. We would like to add Koko Analytics as an optional tool for all of our book authors, but when we recently activated the full Koko cron for all the books/networks on our staging server, the every minute cron job consumed an enormous amount of CPU (close to 100% for about four hours) before stabilizing. The CPU appeared to be within accepted usage for about an hour and a half before starting to spike again. We decided that the CPU usage was too concerning and turned the cron job off for our server. We’ve read other support tickets that seem similar/relevant, like https://wordpress.org/support/topic/days-of-stats-in-only-one/ and https://wordpress.org/support/topic/does-koko_analytics_aggregate_stats-need-to-run-every-minute/ and https://wordpress.org/support/topic/modifying-the-widget-feature-request/. Basically, we’re trying to determine whether we can safely use this plugin in our situation (multiple WordPress multisite networks on a server, each with dozens/hundreds of individual sites) and how you might recommend modifying/structuring a cron job to scale for our needs. Thanks again for all you do to make privacy-respecting web analytics easier!