The both of the web pools actually share the same database server; so you are technically not allowed to create a user on pool2 with the same username.
Just go ahead and use it, and tell me if you see anyting wrong with your HPS2.
Everything has been fine for a solid week now, looking good.
Fixed, It seems the problem was on browser side with different cached credentials for each pool.
Version 139
"hashps": 94984.67855903519,
HPS2 1/3 of HPS with genproclimit=12 on xeon.
Close to 1:1 on non-xeon processor.
Compiled latest version (wallet_fullversion": "1.0.4.0") after xeon fix, same results or worse HPS2 after several minutes.