A bit late to the party but... I am in the same boat with Waves.
Waves are great plug-ins, but to say they do not play well with others is an understatement.
Using this one ... WaveShell1-VST 9.92_x64.dll
That is just making a call back to the mother ship (the actual install directory is in
Program Files (x86)) where all of the actual dll's and exe's reside. All of the x86 and x64 dll's are in that directory also, but when loading those dll's from either x86 or x64 steinberg directories, they do not simply call for the plug-ins. They are calling for a ton of other junk that is the Waves back-end. They are very 'special' like that.
I spent some time trying to figure out the calls made when trying to load a Waves plug-in, and while they probably have their reasons for what they are doing, I hate those reasons. They have built a huge and complex proprietary back-end that they are apparently pretty proud of, and so far I have not been able to get them to load with anything other than what they specifically state their plug-ins are compatible with. Most DAW's that should have no problem choke and die on those plug-ins too.
As a matter of principle (the fact that I spent a lot of money on something that I should be able to use like this and can't) I will have to re-visit it again.