Takes ten minutes, or more, to stabilize when some wanker with a abnormally large hashrate joins, bah. -_-
I'll take that as a compliment.
Technically the overall pool hashrate should not have changed. I actually have 2 p2pools. One cloud hosted public one, and a private one on my own network. Normally I connect my miners to the local one here. But the two nodes are linked together, notice that the pool rate remains unchanged? I just switched the node I was connecting to. Your payout amount and frequency should not change either.
I'm trying to see if I can correct the efficiency rating of the pool by throwing hashrate at it. So far it's working.
I'm curious, what do you see on your end when the local rate suddenly jumps like that?
All I really see in my miner is" Pool Difficulty has changed to xx.xxx" "Stratum from Pool requested work restart" and it just keeps spamming over and over as it tries to stabilise. I have no idea if I'm solving anything, as nothing really pops up. Or are you asking for something else?
.. 
