I don't think so. This pool earlier was showing nethash too high, until a correction was implemented:
I review source code , const uint64_t DIFFICULTY_TARGET = 175; // seconds
Our pool Adjust parameters. thinks all.
I think it is possible he implemented this correction to the network hash, but not his pool hash. So his pool hash is still over-inflated a little.