external-dns.alpha.kubernetes.io/target on Gateway API hen using AWS LBC is redundant

[FernandoMiguel]

I'm confused about the redundant use of the annotation external-dns.alpha.kubernetes.io/target when using Gateway API on an EKS cluster with AWS LBController

AWS LBC will create the LB and update the status of the Gateway object, but eDNS still requires the use of the annotation with the same information

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  annotations:
    external-dns.alpha.kubernetes.io/target: alb-12345678.us-east-1.elb.amazonaws.com
spec:
  gatewayClassName: aws-alb-gateway-class
  listeners:
  - name: http
    protocol: HTTP
    port: 80
status:
  addresses:
  - type: Hostname
    value: alb-12345678.us-east-1.elb.amazonaws.com

This requires us to use a kyverno mutation, just to add this bit of information that is already available in the same object.
Can this be somehow pulled from the status directly instead of having to add a static annotation?