-snip-Although I also found this site
https://reinproject.org/bitcoin-signature-tool/#sign, which I can use to sign and verify messages, after signing the message and trying to verify it, the Bitcoin wallet address has again changed to the first one from the Ian Coleman site.
I checked the tool and all it does is to automatically derive the p2pkh address from the provided private key, it doesn't take an address input.
So you couldn't have used the native SegWit address to sign the message in the first place.
Also, for the address that you mentioned that changed to the one in IanColeman:
It can't be the same address from your BIP44 derivation path since the private key from BIP84 derivation path should be different.
If you provided the prvKey of your native SegWit address derived from seed with BIP84 derivation path, the tool shouldn't derive your legacy address from BIP44 derivation path.
It may look similar because the tool only derives addresses that start with '1', maybe you just mistook it for the first address.