So there isn't a bios patch for the V1 everdrive available for it to make it okay to leave it inserted?
Honestly, I wouldn't worry about it too much on a TED v1, because the fix (i.e. removal) probably causes as many long-term problems as the bus-fighting.
What we're trying to avoid is having two devices (the DUO's RAM and the TED) driving the PCE's data bus at the same time.
The problem is likely more severe on the TED v2 which uses onboard 3.3V RAM (and doesn't clear it) together with level-shifters. That combination is pretty-much-guaranteed to fight with the PCE, and a lot of them are extra-thick cards which are much more likely to damage the PCE's HuCard connector over time.
Luckily, it's easy to fix by using the modified BIOS.
The TED v1's circuitry is much simpler (just an overdriven 3.3V flash chip IIRC).
There's less to damage, and I *believe* that Krikzz actually wipes the entire flash (leaving $FF) before programming the new HuCard image, which will avoid the worst of the bus-fighting.
It's still a problem that a good designer would not allow in their design, but AFAIK it's much less likely to damage the PCE.