We have a bunch of tree farms which generates millions of records about #dispenser destroying and placing spruce_leaves and make the database over 70GB.
#dispenser can't be disabled because some of the machines depends on dispenser and powder_snow.
minecraft:spruce_leaves can't be disabled because we use it to make waterlogged leaves for farms and to stop mob spawning.

Another example is cobblestone generator. We have SlimeFun in our server which needs a lot of cobblestone for ores, so player have built a lot of cobblestone generators. It produces #lava breaking lava record and #lava placing cobblestone records. #lava is required for rollback when lava breaking redstones and other things. cobblestone is required when somebody messing around.

Due to the amount of records, the SQLite trigger before insert on co_block is slower then tree growing.

One way to add this feature:
Allow detailed filtering to blacklist.txt like user:#dispenser action:block includes:spruce_leaves

Other suggestions:
Move bone-meal-grown trees to #tree user. Cancel destroy and place record if they occurs at the same tick and the block are the same.

Use move action for (sticky) piston moved block, sand/gravel drop, dragon egg teleport.

Use replace action for destroy and place record at the same tick and different block.

I strongly support the introduction of the ability to add detailed filters in the blacklist.txt file. On a server with SkyBlock mode, income farms such as mob, creeper, cactus, melon or pumpkin farms generate huge amounts of events, which causes CoreProtect to take up disk space very quickly. Currently, I cannot disable some functions in the config.yml file, because they are crucial for other mechanics, but such a detailed list would allow to eliminate unnecessary entries (e.g. #dispenser destroying spruce_leaves or #lava placing cobblestone) without losing key data during rollbacks. This would be a huge relief for both the database and server performance.