Is this a strong protection feature?

Firstly, I know I haven't got any code here, I needed some help with the idea and I have seen it being used elsewhere. Bascially, you inject an inject into a random process that then manually maps the DLL into the game at launch? I assume this stops the detection of the injector?

I have seen this used on p2c websites but I am not sure how it would work. Surely VAC would still be able to see that a program is injecting something into the game.

Also how would I got about doing this. Just LoadLibrary my other injector into the program, keep looping through the processes until CS:GO is open and then inject it?

Honestly, just keep your stuff private and you will never have to worry about VAC.

As long as you don't use a public injector you should be fine.

I've used the same injector for over a year. It's super simple, just CRT LoadLibrary at game launch.

Reflective DLL injection is basically what you looking for. You inject DLL to some process, e.g. Skype and then Skype injects DLL to game. So game thinks it's some Skype's overlay, etc.