Reconsider use of Activities for error logging to play nice with CRM

Several releases ago you started requiring Activities (tasks & events) be enabled on numerous custom objects, for error logging. I don't think you considered how that would diminish the user experience for CRM users trying to log activities to Opportunities and the like.

The standard Activities functionality has a purpose, "Represents a business activity such as making a phone call or other to-do items."

https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_task.htm

Every object enabled for Activities is added to the polymorphic WhatID relationship on Task/Event, and it makes a huge mess to have many of the Accounting Seed objects in that list. A user logging an activity to an Opportunity has to scroll past entries like Billing Lines, Account Payable Lines, and some ~50-100 other objects that make it hard for someone to find what they are looking for.