Hi, @mkarsten. This rationale may be a bit outdated, but from my prior conversations with the deliverability team, this particular kind of property won’t be built. An email’s bounce status is an extremely fluid thing, and is a function of a lot of different criteria. As a result, values could conceivably change frequently, causing users to take potentially-misleading actions.
From a quick look on the Email Events API, there may be some endpoints containing some of the information you’re looking for in the Bounce delivery event, but I’m not certain it’ll have everything you need (and that’s assuming your org has the developer resources available for a custom-built solution).