I have no plans to add such a sensor. Although the astral package has a “time at elevation” method, it does not have the same for azimuth.
If your plan would be to use the sensor to trigger an automation, then you can just trigger on the azimuth value directly instead I would think.
Azimuth can also be made with a template sensor. Anyway, it is strongly connected to time of day and does not change much through a year. So if accuracy of around 20 minutes is ok, one could also use GMT time.
Apparently, I’ve been remiss in announcing a few bug fix releases:
20240512 Released 3.3.1
Fix processing time_at_elevation config when value is zero
20240531 Released 3.3.2
Move zoneinfo & pytz file I/O to executor
20240813 Released 3.3.3
Fix en translations for nautical_dawn & nautical_dusk