Firstly, congrats on the "new" SSD, as you've seen it's made a major difference so that's great.
I would say not to worry much about the lack of TRIM support, your drive almost certainly has a function called "garbage collection" built in which essentially is a much less aggressive form of TRIM which takes place whilst the drive is idle. If you're worried about the performance degrading, just benchmark the drive every so often and see how it's holding up - maybe every 2-3 weeks, just to see if anything's changing. It does vary from drive to drive depending how good the garbage collection routines are, but you should find that for normal use, performance won't degrade. If it does, you have two options - either try to help the drive's garbage collection out by leaving the drive idle, e.g. by leaving the laptop in the BIOS for a few hours so that the drive isn't being accessed at all, or take an image backup, secure erase the SSD, then restore from the backup. Obviously the latter is much more time consuming, it also shouldn't be necessary.
Windows 7 doesn't really need any special tweaks to "optimise" for SSDs, but let me just quickly run through the suggestions you've mentioned below.
shrinking partition by 8-10%
If you wanted to "overprovision" a drive, this is how you'd do it - well, you'd want to secure erase the drive first, then during Windows setup, create a partition that's around 10% smaller than the total drive space. This leaves that unused space free for the controller to use to allocate writes across, and can supposedly extend the lifetime of the drive. Realistically, there's no way you'd "wear out" an SSD so the claims of extending lifespan aren't something the average user would see. If you had a specific, write-intensive workload, then this may be of use, but you'd probably be better off with a modern enterprise-class SSD for that, or at the very least an SLC-based drive with much higher endurance. In other words, this suggestion doesn't make sense for 99.9% of use cases, so I wouldn't recommend it.
setting static pagefile
If you have a lot of RAM, the page file Windows creates can get pretty large, so you may want to set this to a specific size to free up some space, but that's the only benefit of this. With 8GB of RAM and a 128GB drive, you shouldn't need to do this, I'd leave it alone.
disabling hibernate
Again this is mainly for freeing up disk space, in your case it would save you 8GB (equal to the amount of RAM you have). If you don't use hibernate, by all means disable it to get that disk space back.
system restore
If you're desperate for space, maybe...again I don't see much point in this but if you absolutely, positively will never have to use a system restore point or restore a previous version of a file, go right ahead. By default system restore won't take up more than a certain percentage of drive space so it's not like it's going to go totally out of control, you can always limit it further if you want to (any restore points that take the disk space used over this threshold will be deleted).
vss/vsc
Guessing this follows on from the above, same answer.
drive indexing
Not sure why this is often recommended, I leave it enabled since searches take longer without files being indexed.
defrag
Windows 7 will detect an SSD and won't defrag it automatically, no need to do anything with this.
search
Guessing this is related to indexing? Again I don't see why this would be disabled.
superfetch
Windows manages this and "knows" what to do with it, no need to mess with this.
prefetch
As above.
readyboot
Readyboot or Readyboost? If the latter, this is something you'd have to manually set up, it provides no benefit on the vast majority of systems so just don't set it up.
file compression
I've seen this recommended working on the theory that as drives and CPUs have got so much faster, compression doesn't have a huge impact on performance and can save some disk space. If you need the disk space by all means play around with this, but I've never found it to be too worthwhile.
write caching
If this is the setting in device manager to enable/disable write caching, this is normally enabled by default so there's usually no need to change this. It's a quick and easy change to make and revert so feel free to experiment though.
hdd shutdown timeout
I always set this to 0 (disabled) for SSDs, without doing some Googling I don't know how extensively this has been tested but I know there have been some issues with certain models and power saving modes, considering how little power SSDs typically use anyway there's no great benefit to letting it shut down even if it can do.
The thing to bear in mind is that SSDs have been fairly mainstream for around 7 or 8 years now and they've changed massively since 2008/2009. At that time, there were many suggestions floating around based on various theories, not all of which were right, added to the fact that some of the early "mainstream" SSD controllers just weren't that great, which means that there are a vast amount of tweaks, tuning guides, and so forth which are often just regurgitated across different websites from time to time. That's not to say it should all be ignored, but nor should every guide be followed blindly - so, you're right to check before just ploughing ahead with it all. Hopefully this has been of some help and hopefully it makes sense! Others may have further info to add to this but feel free to post back with further questions or if you need further clarification on anything.
