Trouthunter,
I can’t speak to why the attribute was specifically called legacyExchangeDN and not msExchX500DN. However I can reason it was not listed as a X500 address in the proxyAddresses list because we would need to map a single X500 address back to Exchange 5.5, and the proxyAddresses attribute is a Multi-valued string. It would be easy to have multiple X500 addresses defined within proxyAddresses, and then how do you decide which one maps back to Exchange 5.5? Think of it how you can only have one email address that replicates back to 5.5 Site Addressing specified in a Recipient Policy that is scoped to an Exchange 5.5 site. The restriction is present because of the design of the legacy product. By this you could certainly reason that since Exchange 6.x is dependant on that attribute, later versions of Exchange may very well still have the legacyExchangeDN attribute present and used—but at this point it truly is speculation.