For example, if your wallet client uses a non-compressed public key to generate a Bech32 address, the network considers it nonstandard.You need a miner to be willing to manually include it in a block that they mine.
Correct me if I'm wrong, but in such a case you would have no problems sending coins to such an address, and the problem would only be manifested when you tried to spend the coins on that address. The vast majority of people who make a test transaction simple wait for the coins to show up in their wallet before sending the rest of their stack, and so a test transaction achieves nothing in this case.
Or, worse off, if the transaction is valid but the developers accidentally makes the transaction reuse the r value. The latter is quite unavoidable and can happen after several iterations of the wallet but it is a good way to tell if the wallet is suitable from your first try.
Again, how many people making a test transaction even know what the r value is, let alone how to check if it has been reused? If anything, making a test transaction from one address to another before making a main transaction between the same two addresses puts you at risk of the sending wallet reusing the same r value with the same private key, someone being able to deduce that and double spend your main transaction before it confirms (highly unlikely, I know, but possible).
I have never once made a test transaction and I have never once lost any coins. Care and due diligence in your wallet selection and transaction details are all that is required.