I hope there is going to be more work in the area of exceptions. Excluding only to the recipient's email address is seriously weak. Example, we have lots of cloud services, Azure, DATP, MCAS, and other non-microsoft services that generate email from external, that we do NOT want our current "External Disclaimer" to be stamped on. In those cases we use an exception based on the DKIM signature. You also may want to exclude IP based on sender's IP range.
We are a college and it would be simply chaotic to have emails from Blackboard or Canvas, for example, to all suddenly be labeled in this matter would scare recipients into thinking these emails are not legitimate. Having the robust range of options in a transport rule, will keep us from using this until there are better exclusion options for this new commandlet.