And some of them were spent, including that one: https://mempool.space/tx/6a26d2ecb67f27d1fa5524763b49029d7106e91e3cc05743073461a719776192
Per BIP16, I think they should be treated as simple hashlocks, i.e. if they have a redeemscript, it should not be evaluated, as bip16 wasn't active yet. But block explorers like mempoolspace display these txs as if they are P2SH spends, i.e. they DO evaluate their redeemscript. (See screenshot.) I suspect that's a bug.
