It's strange then that having added the two executables (presumably one of those is responsible for that hooking and patching of winsock. Which again we need input from goldentequil about the contents of the behaviorshield.txt file.
Thinking again about the hooking of winsock, I wonder if one of the settings in the behavior shield might be more geared up to stop this, 'Monitor the system for unauthorised modifications' see image.
So goldentequil could uncheck this option in the Behavior Shield and see if that resolves the problem, if not Set the Action to take to Ask so he can at least see any intervention and authorise it or not.
Well that's me for the night, 4:10am here, hopefully one of the mods/devs can pick up on this later.