You're going to significantly shorten the life of your turbo trying to force it to push that much boost while the cat is restricting it.
If you try to run a tune designed for port injection without port injection you'll run lean as fuck and burn up a cylinder. Not everything is purely about...
DWP is likely what gave you the tuner code. I'd still not run map 3. It's 6psi additive. If your DME requests 16psi for whatever reason, the JB4 is going to try to adapt that up to 22psi.
Map 3 is generally not safe to run. It's an additive map that can push the car a bit too far. Some logs might look great, but get some rough fuel or any number of other things and you can be in a bad spot.
Is a fault code. Likely happened if a sensor was unplugged while the battery was plugged in. You'll see a ton of fault codes if you scan often. It it's something to worry about, you'll get a CEL and then it's time to scan.
The actual value of the code is: "Intake air temperature sensor: Short...
It doesn't matter what map you use, you'll get that fault time to time.
But I don't believe that fault should throw a CEL, if it does clear it. JB4 is telling you to ignore it.
To clear codes, toss the car into diagnostic mode, connect to JB4 and hit 'Delete Codes.' Nothing interesting here.
Like I've said before, I could be wrong. We'll have to wait for Marin or @Jesse DaBears to weigh in. If only the maps are writeable, I think it's pretty basic. But you'll get the power.
WinOLS will write to the 'third' area of memory in the ECU, not the bootloader or the secondary area of memory where things more complex things like on-the-fly map switching would take place. See my post here for some more information on that.
According to Femto, milage is not a problem, neighter is engine hours, but engine hours will not sync. As soon as you start the engine with the new ECU, the old ECU will no longer accurately report running hours, and shouldn't be used - especially for warrnaty work.