The texture hash is calculated from the actual texture found on the game disc; the arrangement of pixels and format determines the hash, so there will never be a duplicate unless the textures are identical (in both pixels and format). The tlut hash is calculated from where Dolphin finds it in the lookup table. Paletted textures can contain multiple textures within a single texture file on disc, and it is these textures that the tlut is included. Many textures, especially those from the same paletted texture, can end up with the same tlut hash, but they will never end up with the same texture hash.
For example, here's a couple of textures that all share the same tlut.
tex1_16x40_0a20e270e3deaebd_ff27218506d334d8_8
tex1_16x40_6c195fda7a018785_ff27218506d334d8_8
tex1_16x40_80a38d424ce271a2_ff27218506d334d8_8
tex1_16x40_205b27b30a8ae0fb_ff27218506d334d8_8
tex1_16x40_d94b9697ce6ae77c_ff27218506d334d8_8
![[Image: KvFhQcK.png]](https://i.imgur.com/KvFhQcK.png)
Allowing a wildcard for the texture hash in the example above would create conflicts and load the wrong texture 80% of the time. So in short, allowing a wildcard for the texture hash would create more problems than it would fix. And since the texture hash will never have a conflict, it is fine if the tlut hash is not included.
In your example, the same texture keeps popping up in different places in the lookup table. I don't know if there could ever be a fix to that, aside from dumping every possibility.
For example, here's a couple of textures that all share the same tlut.
tex1_16x40_0a20e270e3deaebd_ff27218506d334d8_8
tex1_16x40_6c195fda7a018785_ff27218506d334d8_8
tex1_16x40_80a38d424ce271a2_ff27218506d334d8_8
tex1_16x40_205b27b30a8ae0fb_ff27218506d334d8_8
tex1_16x40_d94b9697ce6ae77c_ff27218506d334d8_8
![[Image: KvFhQcK.png]](https://i.imgur.com/KvFhQcK.png)
Allowing a wildcard for the texture hash in the example above would create conflicts and load the wrong texture 80% of the time. So in short, allowing a wildcard for the texture hash would create more problems than it would fix. And since the texture hash will never have a conflict, it is fine if the tlut hash is not included.
In your example, the same texture keeps popping up in different places in the lookup table. I don't know if there could ever be a fix to that, aside from dumping every possibility.
