mariadb filesystem size increasing for wp_options.ibd files

I'm in a situation with a wordpress site where a table wp_options keeps increasing in filesystem size really fast even though it only has 10000 records and we have to constantly optimize it to reduce the usage.

It's my understanding that when records are constantly deleted / inserted they are not actually deleted from the ibd file but they're kind of soft-deleted.

Thus the filesystem size on the file actually increases constantly reaching even 500G within 2 days.

In order to fix the issue I need to actually see what is being written / deleted from the table constantly to find possible plugins that might be affecting it.

I can safely assume it's wordpress transients however I can't say with certainty which type of transient is causing this bloat without examining the data.

So in order to find this out I'm looking for ways to read the soft-deleted data from the bloated ibd file.

I've tried a couple of tools like undrop-for-innodb but it's not yielding any results.

Any ideas how I can read the mass of deleted data that's occupying the filesystem space?

I also think that there should be a limit to the expansion of the table with deleted data. Like, why would a table of 20MBs in size need 500GB of deleted data in the filesystem?