Everyone has this problem. But it's been largely solved in practice by performing the schema changes on slaves, and then promoting the slaves to master.
Also, if you're just using RethinkDB as a delayed (and almost certainly inconsistent) secondary storage system, why not use ElasticSearch instead?
BTW, 250GB fits in memory on any decent size box. You're not really going to see how things scale till you get into the terabytes.