This has been clarified and explained by the forum members. The FAA doesn’t distinguish between the versions of the Evo 2. Since the Evo 2 V3 will be made compliant the whole aircraft family seems to be listed on their side if you don’t look at the serial numbers in detail. Autel however will not come up with a solution for V1 and V2 aircrafts, neither will they officially approve or disapprove of third party solutions. You won’t get any satisfactory answer from either side. Autel is not legally responsible for making their older hardware compliant (even if this sucks, it’s now a fact we have to swallow).Not much communication between the out of touch FAA and drone manufacturers. According to Autel CS the EVO 2 does NOT have RID, and as the CS person told me, "You are on your own to find a compatible RID."
The FFA will not be going into further details other than there are EVO 2 frameworks known that will be compliant. So therefore it’s listed.
See it positive, see it as a wildcard for owners of older aircrafts, if you own an V1 or V2 version, without RID supported by Autel, adding external RID to it as an add-on module, this should give you leverage in any future dispute. It was listed by the FAA when you flew it with the module.
I see a loophole we can use to keep flying our current versions for a while longer. Yes it will cost us some $ or € to add our own solution.