Based on what we were told by Microsoft, the only issue with TRIM was that after successfully running, it soon displayed in the user interface as if it had never been run. It actually worked properly besides that, so no harm was being done to SSDs.
I just let it run as scheduled, in the background, and almost never check defrag in the user interface.
Since then it has been resolved with a CU to properly report in the user interface that it has been run before. That is assuming that you can get that CU to actually install.
Hopefully tomorrow's CU will work better . . .