Not sure how to put this in sorry noob alert
I can see your hashrate on the pool now, if you adjust those settings you should see the rejects drop to 1% or less.
If you have any problems let me know, also, once you get more comfortable with bfgminer, if you do alot of pool/coin switching look into nates multiminer, he has done a wonderful job reducing the headache of mining multiple coins/pools on the same rigs and not needing an army of .bat .cmd or .conf files cluttering up your desktop/folders (it runs bfgminer in a shell, it is sort of like a suite of enhancements and a gui for bfgminer)
try scantime 1 expiry 2 queue 0 I find that works better than 1 1 1 if you were on default teh settings were scan 120 expiry 60 queue 0 (bitcoin default)
exactly when a block is found will be inaccurate until more time has passed since joining. You are likely seeing the amount of time for the pool as an average. It is a matter of % if you are 70% of the hashpower on a pool getting blocks every 2 hours you get 70 coins 12 times a day vs being .5% and getting coins every few minutes but it being .5-1coin I assume you are on pity the pool as that is their blockrate at the moment. It is also important to divide the hashrate for many reasons (noone benefits if the coin is vulnerable to 51% attacks etc). I like small pool high variance myself, as I tend to see more coins ultimately. It is hard to properly evaluate any pool in small time chunks, I like to observe 6+ hours of mining at least to start making comparisons.
http://nwoolls.github.io/MultiMiner/ https://bitcointalk.org/index.php?topic=248173.1960