Instruments changed at 574813 and the map's base architecture most certainly is simply different to accommodate those.
There is no reason you could not transcribe actual tables from one generation map to the other, if you wanted to.
It's actually very simple process in TuneECU:
1. Open the Map generation that matches your range (e.g. 20352)
2. Compare File you wish to transpose (e.20772)
3. Use F6 key to toggle display between the two maps
4. Toggle to 20772 with 'F1' table displayed and then from 'Edit Menu' -> 'Copy Table'
5. Toggle to 20352 with 'F1' table displayed and then from 'Edit Menu' -> 'Paste Table'
6. Repeat for ALL of the other tables
7. Toggle to 20352 and open 'Map Infos' from 'Display' Menu
8. Enter details of your map config e.g. Tables from 20772 transposed into Base Map 20352 5/14/17.
9. Save custom map (what used to be) '20352' with a new custom name of your choosing.
^ This will give you the same performance as the later donor map, but preserve the correct communication protocols for the instruments of the earlier generation Roadster.
Probably of even more benefit, is for Touring Model owners and you can use same method to transpose a Roadster map into your base Touring map!
Incidentally when comparing, any different cells between the two maps will be highlighted with a dot in the corner; just comparing the two maps used in the example, there are actually only very minor differences from the earlier to later generation 'base' Roadster maps - the MAP sensor 'L' tables have slight difference and the I3 table is also slightly different.
(and of course you can equally do the process the other way round, swapping tables from an early generation into a late model base map)
I just used the base maps to illustrate the methodology, but typically you are going to use one of the custom maps to transpose into the base OEM map
