I think you make a good argument given you work in an environment that does solo programming with asynchronous pull request reviews. But I think there’s something even better.
In 2010/2011, I worked in an XP environment coached by Pivotal Labs. We pair programmed so every line of code was code reviewed (indeed, coauthored at every step). We would just run the specs and commit to master about once an hour, so no need for a “merge strategy”. I found this to be much more productive.