Hi Matan,
Thanks for your continued interest in WiredTiger!
The "active" block handle is indeed where new writes will go. This stands in contrast to writes that have been performed, but need to be flushed. Note that a flush happens after the data is on a local disk: the flush operation moves data out to some other "tier" of storage, so isn't strictly required for durability. It's been a little while since I touched this part of tiered storage, but my understanding is that switching dhandles means new writes go to the new file, and the flush is scheduled as future work for a later stage of checkpoint. Hopefully this explains why I think your two statements are true, but not contradictory - if my explanation is unclear or I've misunderstood your question, please let me know.
As for configuration - no, unfortunately this isn't configurable. May I ask why you're interested in changing this? Perhaps it's possible to address your needs some other way.
Regards,
- Will