Please don't spread fud before researching. To start off, the network had been under a transaction flood attack (and not an own overpower attack, if this thing even exists) during the last days. This caused many issues and the team had to shut all the nodes down temporarily until the issue was resolved/blocked. Now everything has started working again.
None of the pools are owned by the coin owners, and none of them refuse connections (tested, it's most likely an issue on your end, or you didn't even try).
Lastly, you keep saying about ASICs, I'm sorry to inform you that ASICs for the CryptoNight Turtle algo (the one the coin uses) have not been manufactured.
Different is when you allow as a code developer a coin to allow ASIC mining while you sit on ASIC's. Then allow blockchain to allow the mined coins with alternative trust. Then, in fact, allow this to happen.
I do see this as possible when some of the nodes still can accept this possibility for accepting these blocks. You don't even need 50% of the network. Just code fix for certain nodes and some of the network. Which in fact were 90% of users don't compile own code?
Even if the source is available there might always be possible to inject a code which isn't traceable for this possibility. Hopefully, there might be someone who can confirm this in the future.
As of what I talk about is not about ASIC mining itself, but code which has the possibility to the owner of the coin to mine ASIC by himself as he wrote the code, and allows certain other algorithms to pass in into blockchain.