2. Then USDC is irrelevant and you shouldn't have brought it up in this context.
3. Fees are irrelevant; worldwide is irrelevant; "10 seconds" is the wrong category of speed: throughput rather than duration.
Though 10 seconds isn't even fast in this context, payment cards are routinely used on e.g. the London Underground at the turnstiles, and anything over about 2 seconds would look like an error and that en-masse would cause noticeable queues getting into or out of the system and corresponding city-level commuting delays.
And normal card use in London public transport acts like a smart contract, as the fee isn't known on initial use, but when exiting the transport network later. Similar on hotels, from what I hear, though they handle it differently.
Both of these have a broader problem: anything on credit (which these function like as the final bill isn't known at point of sale) is fundamentally not part of the blockchain system, so even with all that, all credit cards need something bank-like (and if you use a smart contract to simulate this, you're taking on the risk of bugs in the contract).
From what I understand, TfL actually does all the hard work themselves and figures out the bill later, so if their DC went down the same time as Revolut's they'd not work even if this was a crypto solution that solved every other issue.