SES Domain Identity DNS confirmation failures when multi-region, multi-value MX, active-active

The DNS validation business logic AWS SES uses to verify a domain identity with a custom MAIL FROM gets a bit tripped up when finding a multi-valued record result. Starting from a working and validated SES domain identity with custom mail from identity in us-east-1, when I attempt to add one in us-east-2 and likewise update global Route53 MX records for inbound and feedback smtp endpoints, the SES validation logic declares a failure to find the correct MX records and marks both regions' SES identity domains as not verified. Even though both are listed in the multi-valued records, it fails. (It feels like it's using string.equals versus string.contains.)

This is some example Terraform HCL which demonstrates the core issue of multiple MX records causing SES to fail verification, but would need a bit more structure to be standalone:

resource "aws_sesv2_email_identity" "default" {
  email_identity         = "example.com"
}

resource "aws_sesv2_email_identity_mail_from_attributes" "default" {
  email_identity         = "example.com"
  mail_from_domain       = "mail.example.com"
}

resource "aws_route53_record" "inbound" {
  name     = "example.com"
  ttl      = "86400"
  type     = "MX"
  zone_id  = "Z0123456789"

  records = [
    "10 inbound-smtp.us-east-1.amazonaws.com",
    "10 inbound-smtp.us-east-2.amazonaws.com”,
  ]
}

resource "aws_route53_record" "feedback" {
  name     = "mail.example.com"
  ttl      = "86400"
  type     = "MX"
  zone_id  = "Z0123456789"

  records = [
    "10 feedback-smtp.us-east-1.amazonses.com",
    "10 feedback-smtp.us-east-2.amazonses.com”,
  ]
}

Making these MX records multi-valued seems to be the trigger here, even though I have configured what ought to be a perfectly acceptable MAIL FROM MX record—heck it should be preferred since I am giving customers trying to reach me multiple avenues to connect, even in the face of region-wide failure—it is rejected by the SES DNS validator.

I sincerely hope I have got something silly wrong here, otherwise it implies that NO_ONE using AWS SES has an active-active setup for email receiving for any given single mail destination (as AWS SES will mark it as unverified and unavailable for use in all regions). I find that too difficult to believe. Will someone please spot my error? I’m really stuck.

Thank you.