The goal to bump boost minimum is not just because of this issue but because as the rest of the world move it’s boost dependency up higher, the spread in API issues increases. Boost doesn’t do their API versioning using semver style so even a change from 1.67 to 1.68 of boost can have major API changes just because some maintainer of a boost package felt so. On our main supported platforms we are all >= 1.70 so are moving the baseline up.
As we move the baseline up, it also becomes possible to use newer boost packages that exist now and didn’t before.