…then you should configure a redirect on your production server.
A Hugo alias will not work because:
With Hugo, you can only create aliases with an html extension.
Even if you could create an alias for the xml file, the xml consumer (browser, aggregator, etc.) wouldn’t honor the meta http-equiv redirect. Or to put it another way, there’s no provision for content refresh/redirect with XML.
Ah, that’s a shame. It was a legacy feed location feeding some other processes that necessitated having it in that location. The feed location had to be updated on the other processes.