yeah a lot of non-standard scripts are going to be rejected by all bitcoin core nodes with default setups right away on mainnet and only partially on testnet. it is a good thing too, it prevents malleability attacks, sending coins to broken scripts and lose funds,... but sometimes it is bad too, there is someone in tech support board that has a large amount of bitcoin (5-6 i think) stuck in a SegWit output that simply uses uncompressed public key.
It is a little strange that the original puzzle transaction, referenced in the wiki - part of Bitcoin's history, is perfectly irreproducible today, with stricter enforcements of IsStandard() and IsStandardTx(), while at the same time these checks have been completely disabled for P2SH. For example:
OP_TRUE
gives locking script "7551", which is translated to its 3-address by
>>> script='7551'
>>> base58.b58encode_check(binascii.unhexlify('05'+ hashlib.new('ripemd160', hashlib.sha256(binascii.unhexlify(script)).digest()).hexdigest())).decode()
'3L7zn1euXPcWoJC36Biw4yXee6F5ksEYdb'
And 3L7zn1euXPcWoJC36Biw4yXee6F5ksEYdb is perfectly legal to send to and spend from, still. To spend, push any single value as the unlocking code, the script will drop it and replace it with "TRUE".
Edit/addition
Have confirmed that the above works (caveat: testnet).
First, calculated the P2SH address for script "7551" (changed prefix from "05" to "c4" for testnet):
>>> script='7551'
>>> base58.b58encode_check(binascii.unhexlify('c4'+ hashlib.new('ripemd160', hashlib.sha256(binascii.unhexlify(script)).digest()).hexdigest())).decode()
'2NBgCqkaw8r7s15pamKLogvWurSTFVVf1Kf'
Second, sent 0.1 tBTC to 2NBgCqkaw8r7s15pamKLogvWurSTFVVf1Kf, txid: 6a9cf36bd72c2b1cba68182b65975a3be95f4aa345fe4c63986117e7489ed572
Third, manually created a raw transaction in which the key (literally) is the sigscript "0451027551", in which "04" is the length of it all, "51" is OP_1 (pushing 01 to onto the stack; this could, however, be any value), followed by "02" which is the length of the locking script and finally "7551" which is the locking script itself.
Broadcast successfully in Bitcoin Core GUI console with:
And so got it all back (well, minus transaction fees), txid: 20ecf01a6be6d9e103732e8ea05f5c504fc403de7cd3f96ca6df8c8853afd2f3
All good. I'm quite sure this is reproducible on the mainnet, but didn't feel like wasting real BTC tx fees for simply amending this post.