I had not even noticed the .exe file size difference! I did have the same concern regarding whether there is any interaction between the two versions but thought at the time I will have to get to testing it somehow, but then noticed that the Indigo editor uses the DBP directory path rather than look specifically for the compiler. This I found suited me best - in my TGC folder the old version is labelled as "Dark Basic Professional Online". So what I used to do I simply carried on doing - I add the version number to the name "Dark Basic Professional Online" and simply keep a text file in the TGC folder which I then make a note of which version I am currently using. So the folders within TGC directory look something like this:
Dark Basic Professional Online U6.x ....and so on
Dark Basic Professional Online U7.x ...and so on(some are name U7.xRCx as I also had all betas installed)
Dark Basic Professional Online Free version U7.5 ...this is the free version of the older compiler that TGC used to provide which they have now replaced with the open source version
Dark Basic Professional Online GameGuru ... this is the open source newer compiler previously name "Install"
So when using a particular version I rename the folder to read "Dark Basic Professional Online" using Ctrl+x to remove version info and then Ctrl+v into the text file I just mentioned so as to keep track. As the Indigo editor is 3rd party and only requires the install path rather than a compiler path, there is no confusion as to which version it is using as it will simply use the contents of "Dark Basic Professional Online" folder I gave it, so I have set just the DBPro files for association with Indigo when opening a project from the project file - I prefer to open dba files in the oldest editor so that the file icon is different, this helps me as I find it visually easier to find the project file if there are lots of dba files in same place as my eye sight gets more blurry as the day progresses.
I used to believe the version info oddity is an editor issue - similar issue crops up with the oldest editor with older versions of DBP being reported incorrectly from what I recall - but then this newer compiler came along and Indigo also reports 7.1 which confuses me. I do seem to remember that the newer compiler originally had to be reverted back to an earlier version of source code before they branched out into creating a faster compiler(for whatever reason - I don't recall), but as this has replaced the older free version which was U7.5 I did expect it to be U7.5 also. I based that on the logic that the older free version was the last version that worked without issues, which also confused me as I had thought U6.9 was the last good version without additional issues! So chances are it is indeed U7.1 that your looking at. Another user(Kuper I think) did mention recently that it can be upgraded normally but this may well only achieve the older compiler version with god knows what differences or further bugs might have been introduced by doing so.
To further add to the confusion you may have noticed by now that for those of us with purchased version of DBP and plugins, we are still waiting for our activation keys to be brought forward from the old websites system to this new one(3 months now!), and so in the time being there is a new activator to download, or so it seems, I checked it out a few days ago, its a blatant lie!!!! It is merely a link to download - wait for it - the compiled version of the open source kept separate from the visual studio project, you know the one that would have been better placed on the product page for new users rather than to confuse the crap out of them by linking them to download the entire lot as both yourself and I have done. It may be the case that it can be updated normally and maybe even works for removing the need to activate plugins once updated to whatever update we choose, but it doesn't account for updates 6.8, 6.9 or 7.0, we are stuck with 7.1 onwards and doesn't even come with some basic instructions! I am not convinced that this hap hazard way of thinking would not introduce bugs by simply overwriting existing installations from our accounts - and I feel like I am being looked upon as an idiot into being tricked to thinking that overwriting one full installation of older DBP with the entire new compilers full version is risk free of breaking older projects. Why provide the original purchased DBP in our accounts along with a message indicating activation keys are on their way if all we are going to do is overwrite all the files with the newer compilers version?! They should have left things as they was in terms of availability, updated the rest of the site and simply added the open source new compiler as an extra option - I think they are trying to move away from the on line key activator, maybe once this new site is finished they will just turn it off but to me that means all those plugins we bought that still require security as the owners haven't given them permission to make them available for free and/or open source, well all it takes is for someone who paid for them to make them available on say a torrent site. I have noticed that someone sold their products as "second hand" on the DBP facebook page, existing customers may be folk who wouldn't pirate products in such a way but all it would take is one of them to change their mind or sell second hand to someone who might do so. The way this has all been done seems somewhat dodgy to me, hide the risk by complicating a process is what it looks like to me.