Missing tokens do not highlight in Cloned Dynamic Programs

In dynamic programs it is very difficult to identify missing tokens in Cloned programs.  We support over 20 languages and have a version of each for each template. Some of our Programs have 5 emails and each email can have 5-8 tokens, meaning this needs to be re-mapped hundreds of times.  Currently, the missing token looks exactly like the mapped tokens in cloned programs, including the required from fields.  See the screen recording on ticket 302972.  The ideal solution is that the mappings hold and do not need to be changed at all.  That allows for accurate testing in a cloned program.  If that cannot be accomodated, or the source changes and the field is truly no longer available, the warning sign should appear and the missing tokens should be red or another color so they can easily be identified and corrected.