Its none of the pool owners fault, the network is unbalanced, and Nitro has more than 50% of the network (No fault of theirs). If the hashes spread out there would be less orphans on the network as I understand it. Nitro's hashrate is so large, they define the network. The hashes need to spread out.

Whats funny is that when Nitro goes down for maintenance, 35% of the miners instantly Failover to our pool (LeetPool), and the orphan rates go down immediately.  

We need the miners to spread the hashes to all the pools on the network, and it will keep the coin healthy.

http://bitgo.pw/utc/ <--- Look at the bottom at the pool hashrate chart.

Since the hashrate is so enourmous as one pool compared to another this happens:

We will solve a block:
http://s15.postimg.org/np4oo5yfv/leetblock.png

Nitro will solve the same block:
http://s16.postimg.org/pa7ttlefp/Nitro_Block.png

See what happens here? Nitro will beat everyone to the punch if they happen to solve the same block as another pool even if we might have solved it first, or if Nitro might have solved the block first, we will be late because the network is defined by the hashrate.

I was talking with TheSerapher in IRC, and he suggested that other pools add Nitro as a node for UTC -- But he did not elaborate on how to do this. If anyone can think of a solution, please chime in.