replication - CouchDB Load Balancing: Primary write-only and Replicas read-only -

we looking @ load balancing our couchdb databases. strategy of having 1 primary database handles writes, , multiple replicas handle reads, seems solution me. site explains pretty well:
https://www.safaribooksonline.com/library/view/scaling-couchdb/9781449304942/ch04.html

however, have 1 nagging thought. if writes go primary, , reads replicas, possible user cause update data , not see right away because of latency of replication? sounds happen every time, if read comes after write.

would useful (or work) include primary in list of servers can read? or useless, or break things worse?