Maybe you missed several of my posts? The end user can remove all of the software that is pre-loaded and install their own. Someone can even create their own menu launcher and make it available as open source. I am not Apple I am not forcing anyone to use the pre-loaded software. I know you guys are use to dealing with anonymous people from unknown countries. However, this is not one of those cases. When the site is live there will be an actual address and contact number. No reputable corporation would ever give out their source code to random people online unless it was open source. The problem with open source in this case, 50 people will copy what we have done and just do the same thing in a week. Is that what you really want? If they want to copy the idea that is fine, but they will have to code it themselves.
As a developer I completely understand. I too maintain a very tight reign on my source code (as it's my livelihood at stake).
On the other hand there are two risks that as a PR/Marketing guy you can understand well... as you've already as it relates to your company and it's reputation... basically brand dilution or destruction.
This is a pretty fine line to walk here. While I'm perfectly fine (for personal use and that of my friends) in being able to wipe and reload at will. With something carrying the BC logo and name... but allowing anyone to wipe and 're-purpose' it remains a potential problem in another scenario. Suppose someone (who is not honest and supportive of BC long-term) purchases a number of the cards and loads a keylogger or similar malware on it, or even more simplistically simply dumps the private keys associated with the wallets... and then hands them to people who then load them up... and wake up to missing BC - the damage would be smaller than a 'Mt. Gox-ing' but could still represent a threat to the brand itself.
On the other hand if the code was 'vetted' by Maarx and Rat4 - perhaps with a MD5 on the site which would be checked to verify that the entire contents of the card (other than blockchain and wallet.dat obviously) hadn't changed since issuance. That might go a long way to assure holders that it was safe to load value onto the card.
Something to keep in mind at least, as although today 1,000 BC might seem like chump-change... it might be a good used car's worth in a year.
The code being vetted would not prevent the scenario you just described.
Easy solution, tamper proof sticker on the packaging
A Must Have !