Sun, you were asking about 'stratum requested a work restart'. So I went through a certain amount of pain trying to reduce the chatiness and learned that in stratum its not as simple as just setting a poll setting and resetting the work restart request (as one would believe because of the interval passing). There are many factors that influence the work restart: rpc polling duration, merkle root changes (or tx list changes), someone mining the current rounds difficulty, stratum timeout between client-server, etc.
1) I am not getting any more duplicate share errors so that is good. Most of my pool mining is ASIC based and I do see the "Stratum requested work restart" sometimes. I'm reading several times per minute is normal.
2) Worker stats seems to reset the hashing stats occasionally?
http://nomp.biblepay.org/workers3) What kind of payment scheme does the pool use? Is it pay-per-share (PPS)? PPLNS?
https://coinguides.org/pps-vs-pplns/4) Finally got paid 137 BBP after 12 hours. So, that is working too...

1) Yes, from what I can see its working properly (even when it resets client work, because its giving fresh work to be less likely to find duplicate pobh hashes).
2) Yes, stats reset when the block changes. We are hashing a current 'round' as a group, then we reset.
3) According to nomps docs, they use PROP which is PPS (payment per share) with a reward for only the miners that were present during the block being hashed. This is very similar to what I did in pool.biblepay.org.
4) Great! Yes, the payments that are emitting look correct now. I don't see any orphans over 24 hours, and all the txids are in the dedicated wallet.