The "problem" with RBRX and TRIM is very simple. It's exactly the same as the relation between RBRX and Defragmentation software : they are incompatible. You can't move data at a physical level on the disk (which both Defrag software and TRIM do) and expect another utility that does the same thing (aka RBRX) not to be affected or viceversa. It's quite logical and doesn't really need "tests" to be proven - it's like expecting two partition managers to work at the same time, for the same hardware and logical devices. The definition of impossible, since they work with the same data at the same time.
Now if anyone looked at http://community.horizondatasys.com/...aggers-support, the HDS answer on both matters is that RBRX "supports" them both. And of course it ... "supports" them The same way (older) Windows "supported" GPUs by installing only a generic driver: the GPU will "work"...only that it won't do what it's supposed to do (e.g. run at the maximum resolution, have all the fancy stuff available in games, etc.) In other words, RBRX will "support" (read "tolerate") both Defrag and TRIM, just that their basic functionality (the whole point of them existing in the first place) is gone.
If you carefully read HDS statements (aka read between the lines - something I'm VERY good at...) you'll notice that in the above link, Nick10, the moderator, states:
"Fast forward to today... Defraggers are now slowly becoming obsolete due to the new generation of hard drives known as SSD. But just like traditional hard drives, there are a new set of utilities designed to determine its data efficiency. However the concept is the same and RollBack Rx behaves similarly."
On the other hand, at http://support.horizondatasys.com/Kn...ng-rollback-rx, Guru Shiva from HDS states that "If you really need to defrag the drives with a third party tool: Uninstall RollBack Rx, defrag the drives and then reinstall RollBack Rx". Now why would that be required if RBRX fully "supported" Defrag (aka Defrag could be able to proper defragment the drive), huh? Classic marketing BS - and yes, I know how marketing works, I've studied that in college quite extensively.
Now if you add the conclusion from my last paragraph to the conclusion of the paragraph before it (aka "the concept is the same and RollBack Rx behaves similarly") it's easy to see where this is going to: TRIM won't do what it's supposed to do while RBRX is running. Yes, it is "supported" (aka "tolerated") in the same way third party defragmentation is: killing its functionality. No test required, just properly read between the lines and be logical.