I can't see your screenshot above (as I just registered to these forums) but looking at the disassembly (with IDA) of several of the program's files indeed shows references to SSD tuning.
e.g. the following in Client\Common.dll:
.method public final hidebysig virtual newslot specialname instance bool get_GetSsdTuningEnable()
That is, the function pushes 0 to the stack and returns, thus always returning 0.
I naturally tried making it return 1 (by setting ldc.i4.1) but it didn't seem to make a difference
I have zero experience modifying windows assembly (not to mention .NET) so I wouldn't be surprised to find out there are various protections for these kind of things (e.g. protected by a hash of the binary) - does anyone here have experience with this kind of things?
I'll do some reading and try to get some more progress