Threads and TQ anti cheat system

Okay, so I haven`t actually tried this, but I`d like to : I injected a DLL in the CO process reading the send and recv functions. Now I`d like to create a two way named pipe within the DLL to communicate with another app, which controls the actual logic, the DLL just extracts data and uses data gotten from the external application. I`d like to create the pipe on a separate thread in the DLL. My question now would be : is it even a slightly good idea to create a new thread inside the CO process, regarding their anti-botting measures? If not, any ideas on how should I go about this?

I would probably create the named pipe in the "remote" program. Then connect to it from inside your DLL (doesn't need to be in a new thread, it could be like ... the first time one of your hooked functions is called or whatever). You can use the PeekNamedPipe function to see if there's any data in your pipe to be read without blocking - you can use that inside a hooked function like ReceiveMsg or whatever - some function that's called several times per frame and then there's no need to worry about creating seperate threads from your DLL.