I am running same as you, but no CPU issues. Support did review my DB and provided guidance on performance improvements:
Last, if you have any collections using the "member of collection" filter, let's change that to its more reliable filter-cousin "computer collection is member" instead. Development has been able to find a performance issue that is directly related to using that particular filter.
Not totally sure why this is not a little more publicized, but sounds like a good way to improve performance. I have a ton of these in my environment that I am starting to remediate.
From Ticket #154507
One of our clever guys here wrote a SQL report to find filters which might need changing:
Select Collections.Name as "Collection",
reportdefinitionfilters.Value as "Filtering for this Collection"
join reportdefinitionfilters on Collections.ReportDefinitionId = reportdefinitionfilters.ReportDefinitionId
where reportdefinitionfilters.tablename = 'Collection'