Garbage Collection works its own work on free moments in time (and very good so in the modern SSDs). Trim does not bring anything more than telling the SSD what can be deleted. May possibly take some moments from the GC and/or create timing issues.
It is impossible to say whether trim does or does not cause issues on a SSD. AS I said before it does not crash a SSD, but it is impossible to say whether it slows down GC or speeds it up thus it's claim that it does brings something is theoretical.
The write speed is and stays good when GC has enough free space to do its job, until the max number of block cleareance is reached.
The Linux kernel list of SSDs is important, why is it there.
What evidence have you shown that trim causes issues?
As for it being not necessary, there are several professional opinions which don't agree with you. For example,
http://arstechnica.com/gadgets/2015...garbage-collection-so-i-dont-need-trim-right/
Here’s the skinny: TRIM is never a requirement, but it always helps, and you’re always better off with it than without it. In this (relatively) short article, I'm going to explain why.
Written by someone who has an extensive background working in enterprise storage security for several large companies.
The linux kernel list is there because
there was an issue with issuing trim commands with certain SSDs which was found to be caused by specific versions of the linux kernel that have since been fixed.
OS X is not Linux. It is Unix based. The SSD issue was with the linux kernel. OS X runs the XNU kernel, which is a derivative of MACH.
It's like saying that the engine from a 2004 Citroen C3 was incompatible with a certain type of oil but this was fixed in the 2006 C3. The Peugeot 308 which shares the same underpinnings of the 2008 C3 but uses a different engine isn't going to inherit the incompatibility from the 2004 C3.