I am not technically skilled enough to go deeper into this issue and say that in your case exactly what I wrote about in the previous post happened, but let's say that there is a possibility that this is exactly the case. Some call it a ransome attack, because the attacker did not steal the coins, but just hid them deep and knows which path they are on. But if no one has contacted you, then it could only be some malicious person or some as yet undiscovered bug.
What is certain is that both major manufacturers were warned back in 2018 of this attack, and that they are both (Ledger&Trezor) reacted with new firmware that was supposed to make it somewhat impossible for the user's funds to be irretrievably lost. What they did was actually to reduce number of key index to the extent that it is possible to break it with brute force.
If you read the link to the change path attack, then you could see something like this 44'/0'/234454354'/545343432/4654657657 , and you see that is an almost impossible brute force with today’s technology.
I guess you have firmware for your Trezor which is v2.0.9 or above (Model T) since they say Trezor One is never been vulnerable. From what I read Trezor should show you
"key index for every address generated", which would mean that you could theoretically find the target path of the address where your coin is located. What I can't say is how to do it, is it possible through the Trezor UI, or should you use some special tool (maybe Ian Coleman tool (use only offline version) -
https://github.com/iancoleman/bip39).
I would definitely send another ticket to Trezor support and shared this information with them.
Another interesting article ->
A Ransom Attack on Hardware Wallets