The setting most people have wrong without knowing it, and the symptom is misleading: the game still opens in VR, but the mod never comes into play. Three clicks and it sticks.
When WRC starts in VR mode it does not talk to any particular headset: it asks for OpenXR, which is a standard socket. Windows keeps a single note of which program is plugged into that socket. That program is called the runtime. It can be the Oculus one, Windows Mixed Reality, Virtual Desktop, Pimax, or SteamVR. Only one at a time, for the whole machine.
TrueTriple lives inside SteamVR: it is a driver that adds a virtual headset to it. If the runtime is something else, the game goes with that something else, SteamVR never finds out the game started, and the mod does not even get a chance to fail: it simply is not part of the picture. That is why the game "works in VR" and at the same time there is no triple: nothing is broken, it is plugged into the wrong place.
The app sets it to SteamVR when you install. But any other VR program can switch it back later without telling you: the Meta/Oculus app, Virtual Desktop and the WMR portal all set themselves as the runtime whenever they open or update. If it worked one day and not the next, this is almost always why.
With SteamVR open. No headset needs to be connected.
How to know it stuck: that same tab should read Current OpenXR Runtime: SteamVR. And in the TrueTriple app, under Install, the "OpenXR runtime" card turns green. If you cannot see an OpenXR tab, set Advanced Settings to Show at the bottom left: it shows up there, or under Developer.
Still not going triple? Back to the quick checks in Anti-bugs: the others are having the three monitors joined (Surround or Eyefinity), restarting SteamVR after saving, and launching WRC in VR mode rather than the normal one.
Screenshots are from LIV's guide, which needs the same setting. They show an earlier SteamVR version; the path is the same in the current one.