No kidding mr Joker. Now you can do that, but not from 2 April 2016.
Mr Elite Reverse Engineer - the watch has a similar file which is just as accessible. It is incredibly easy to fake like I stated (where do you get the Joker thing from and why so defensive?). I am also not convinced that discovery will be able to differentiate between a file upload and watch sync (a manual entry of distance is a different story) as Garmin keeps this in place to support the legacy devices. But time will tell - don't really care either way.
From a nike+ device exporting files to Connect:
<Creator xsi:type="Device_t">
<Name>Unknown</Name>
<ProductID>1</ProductID>
<Version>
<VersionMajor>16</VersionMajor>
<VersionMinor>4</VersionMinor>
<BuildMajor>0</BuildMajor>
<BuildMinor>3</BuildMinor>
</Version>
</Creator>
From a Garmin Fenix 3 (somehow incorrectly reporting the device name):
<Creator xsi:type="Device_t">
<Name>Unknown</Name>
<ProductID>1</ProductID>
<Version>
<VersionMajor>6</VersionMajor>
<VersionMinor>80</VersionMinor>
<BuildMajor>0</BuildMajor>
<BuildMinor>0</BuildMinor>
</Version>
</Creator>
Do you think that Garmin or discovery (not that they receive this info) will be brave enough to classify it based on a version number that can be altered in notepad anyway?
Garmin connect even shows it as coming from an unknown Garmin watch - despite it being a Nike+ device. And you want to do USB sniffing and stuff. lol
All this elite reverse engineering and calling people "Mr Joker" - lol