Hello Justin,
I've played in production a few years ago about the cache in CMOD because a customer had so many problems with disk space, and he couldn't get fresh ones...
so we used arsmaint with option -c and the -t option and we said that we were x month in the future... and also with the -n and -x option (like arsmaint -c -t 15400 -n 40 -x 40 -u admin -p password).
and that worked wonderfully!
My experience if that if you play with -x you need also to take care of -n, they both need to be changed most of the time...
-t was really for some situation where -n and -x didn't do it's work enough for us at that time... I don't advice it, but it might be useful in some cases.
The other way I can imagine... is a bit more... gore... but since you've seen lot in your CMOD trip during the last few years :-D my other idea would more in the direction of
Look in the segment table of the application group you want to remove cache weight, get the doc_name of them.
Look in the cache if they are there, and remove the files (directory too if the directory is empty after the delete operation), and remove the corresponding links in the retr directory in the cache.
That's the options I'm used to use with my customer who wants to clean a bit more the cache that the normal usage...
Sincerely yours,
Alessandro