A lot of these so called tweaks are just personal preferences and not tweaks. Turning of Spotlight is not a tweak. It's a personal preference how you would like your search to function. Anyway. From someone who actually read the thread from the link posted I have one post that actually have knowledge regarding sms. See quoted post below from poster lgerbarg.
http://www.ocztechnologyforum.com/forum/showpost.php?p=368792&postcount=76
When I worked at Apple I was involved with the design of the SMS, and that is not what it does. When the SMS detects a fault it sends an "IDLE IMMEDIATE" command with the unload bit set, which tells the device it is supposed to move its head to physically safe position. You can see all of the ATA stack bits in the opensource ATA drivers. Since an SSD has no moving parts (and thus cannot actually move its head), I imagine it does nothing with it. I suppose it could try to flush its cache, but that is technically nonconformant. The drive stays turned on in all cases, it has to since it might have unsynced data in its track cache.
Okay, so just to prove I am not just a grumpy old naysayer, here are some things you could do to actually improve performance under OS X.
1) Disable Adaptive Hot File Clustering
This is a feature of the OS that tracks how often files are used and automatically moves them closer to the outer rim of the drive (which is faster on conventional disks). On an SSD it is just a useless block move.
2) Disable automatic defrag
This actually might not be a win, because the system only performs auto defrag in very limited cases (files less than >20 megs with more than 8 extents), and while defragging the file itself will not be a performance win, consolidating its metadata into the file record (so you don't have to walk through the extents btree) might in fact be a win even on an SSD because it significantly reduces the amount of reads you have to do figure out where the file is.
The unfortunate thing is that there is no simple way to do either of these. You could build a custom kernel (it is a ~1-2 line change to short circuit them out). I suspect that neither is going to be a particularly large win though, so you are better off just running a stock (supported) kernel.