What I notice is that it gives slush for instance a slice of 300sec(or whatever it sliced at) then it would eventually hop to slush even if its at >10.35% (my example it was at 40%) and then finish the 300sec slice. I think it should be able to notice the pool is assigned mine_slush (or atleast its defined something other than just mine) and clear the slice as soon as it hops there(or before it hops there)
See my posted issue regarding this topic:
https://github.com/c00w/bitHopper/issues/128