In CheckUser we have a config variable called $wgCUDMaxAge which is both used in the maintenance script maintenance/purgeOldData.php to remove old IP data in batch (once they are beyond the maximum age based on data retention policy). It is also used in CheckUser.hooks.php inside the maybePruneIPData() method, where in 1 out of every 50 queries it is used to also prune old CU data in an active fashion.
A similar config variable already exists for AbuseFilter, called $wgAbuseFilterLogIPMaxAge and it is used maintenance/purgeOldLogIPData.php. However, a mechanism similar to maybePruneIPData() does not exist for AbuseFilter.
There has not been a huge demand for it because AbuseFilter's IP data is not available to any user group on WMF wikis as of now. But once T152934 and T160357 are resolved, it will become more important to have an active purging mechanism.
At the same time, while CheckUser is rarely executed, AbuseFilter is very frequently executed; on one hand, it means that active pruning could take care of almost all of the purging for AbuseFilter IP data, but on the other hand, it could mean that the impact of it on processing time can be more pronounced.