Your idea sounds great for OPSEC to proactively avoid Address poisoning attacks, but if I am only a normal Bitcoin user, not a programmer, I just think it's hard for me to intentionally create such addresses.
Of course this would have to be implemented in some sort of program, ideally in a wallet software.
Another strategy just occurring to me, which also is feasible for bech32, is to deliberately use addresses with 3-4 letter patterns at the start, center, and end you could recognize, e.g. those that are similar to names or words.
Simply batch generate let's say 100 addresses and select those with patterns you think to recognize, the center patern being particularly important because the center of the address is often not taken into account by the attackers (they tend to use addresses with similar start and end). It should be very difficult to generate addresses with 9-12 already pre-fixed characters, and in addition the attacker maybe even doesn't know which combinations are the ones you recognize as a "pattern".
This should be very easy to do even for beginners (as long as they know how to batch-generate addresses) and would not need additional software. Wallets could of course offer some kind of "dictionary check" where the generated addresses with combinations similar to words (in different languages) or names are highlighted.
