I'm happy to be wrong, but I believe turning the ordered write_timestamp assertion in WT only results in some extra log messages.
It'd be more easily integrated into testing if we could have it fail transactions or even just crash the process.
If it makes things easier, I don't think MDB has a use for the verbose logging. So if these error messages were followed by an abnormal exit, that'd be great actually.