People have uploaded whole cross-continent bike rides (i.e thousands of km) into my website as a single GPX file. It's not unusual for modern high-resolution GPS routes to have north of 40 points per km (typical for RideWithGPS). Multiply the two and you're easily into six figures, which would be beyond the claimed "tens of thousands" for the Wahoo. Even something relatively sane like LEL at that resolution might cause trouble.
I find that with a lot of the modern bike tech there is often an assumption that noone rides more than 6 hours. Noone rides more than a couple of hundred km, and noone rides when it's cold.
This was one of the problems we saw a lot with Garmin's, they would often crash on long rides, as they seem to have not been tested for such long rides.
As for the Wahoo bolt, I did a ride with 18376 track points, and it seemed to cope just fine.
But I'm guessing that the kids at wahoo haven't tested it with 50000 or 100000 track points.
The limit will depend to an extent on how much ram there is in the device. If each track point is 2 x 32bit floating point (reasonable assumption). That's 8 bytes per point. That's assuming it isn't loading into memory a turn by turn. If so, a 10000 point track would be 80kB. Or put another way, if it has 1MB of ram, that's enough for 125000 points. But if you add some data for turn by turn, it's going to get much bigger. I wonder how much ram it has...
J