> I'm guessing the people that run the pool know more about difficulty requirement for the coin you are mining than a miner.

The difficulty for a block is known, and changes approximately every two weeks.

There are very few pool-specific things that the pool knows that miners doesn't know, such as the pool's current bandwith and CPU usage (both in an absolute sense, and as a percentage of the maximum current capability of the pool), and the number of current miners and their current combined hashrate.

Based on these factors, the pool might want to constrain the amount of communication with each miner.  (It also might not want to communicate at all with some miners, but that is a difficult decision to make that will soon be widely known in most cases.)

There are reasons why a pool might want to increase the amount of communication with a miner, as well.  I think they would boil down to wanting to eliminate stale shares, and to insure that the miner is actually attempting useful work.  In most cases, communication every 30 seconds to every couple of minutes should suffice for both these reasons.

So if a miner unilaterally decides he's mining at a hashrate that should give him a reportable hash once every 30 seconds or so, it's hard to imagine why the pool would have a problem with that.  But, if the pool _did_ have a problem with that, there is already a mechanism to let the pool increase the difficulty (reducing the communication rate) for the miner.