@demion90: Yes, loading DLLs dynamically won't show in Dependency Walker. In that case you'll need some other tool. There's a plenty to choose from. For instance, Sysinternals ProcMon will probably do. It won't show which APIs are used from those DLLs though. For that you'll need to trace it with a debugger and look for LoadLibrary calls.
I do have an old AMD card. What seems to be lacking is time. But I'll try to look into it as soon as I dig through my work project first.
@stash2coin: What do you mean by "ms implementation of socket TLS"
Most all Windows DLLs are MS implementation of something. It all basically boils down to one DLL calling some other DLL internally. In the lower user-mode level any network-based API will eventually call to raw socket DLL (or ws2_32.dll.) In case of those screenshots that you posted (which don't really show much -- you need to see the hierarchy of those DLL calls, in other words, which DLL calls which and also which APIs in each DLL) it shows that in the lower level it does use raw sockets and the following for TLS/SSL stuff: advapi32.dll, wintrust.dll, crypt32.dll.
yesterday found an example code in C++ how to use it, its pretty straight forward didn't saved the link.
You realize that your web browser has the "history" button, right?
@Cyper_BLC: Yes, it would be nice to start a new thread for this. Also if you do, please post a link here so we can follow. I'll let @demion90 do it.