Well, not really. If you intercept the correct WinAPI before encryption you can still inspect and redirect it. Pretty much what you're doing in your DLL. Although I doubt that they would use raw sockets to implement TLS.
PS. I'd test your project but I need to install VS 2015. Why not use an earlier version of VS?
You can try any VS version, it should compile fine (nothing VS 2015 specific as I recall) , just need to recreate project file using existing sources probably.
What WinAPI are used to encrypt TLS? If you mean intercept internal Claymore functions, this need reverse engineering and I am not good at it. Also Claymore Miner is 64 bit and seems to be packed / obfuscated. As stash2coin logs show packet buffer is already encrypted in ws2_32.send (expected) and it also seems like it uses encryption for dev fee even if main worker is not.