The bottleneck is usually in SD card write speeds, however. Sport photographers often skip raw and only use JPG because the files are smaller and as a result, one can take more photos in one burst.
For raw at high frame rates, high end cameras don't use SD cards but things like CFexpress which absolutely can keep up (and there are also various compressed RAW formats these days which apply a degree of lossy compression to reduce file size).
As I understand it, the reason some professional sports photographers don't shoot RAW (or it's less important) is more because they are in an environment where publishing quickly is important, so upload speeds matter and there isn't really much time to postprocess.
Canon’s “sport professional” camera has lower resolution than the “second tier” cameras. It has a higher frame rate and CFExpress and SDXC2 so bandwidth isn’t an issue. Last I checked you could burst 40 or 50 frames (at 20ish fps) before filling the internal buffer.
You can definitely do more than that these days. My Nikon Z8 can do 30fps with 1xCFExpress, and the flagship Z9 can do 120fps because it has 2xCFExpress and alternates writes. On the Sony side they have a closer differentiation to what you describe, the flagship (A1 II) does only 30fps compared to the next-best (A9 III) which does 120fps, while the prosumer (A7 RV) only does 10fps.
I don't know Canon well, but 120fps w/ dual CFExpress + 800-1200 frames buffer is fairly standard on top-end professional sports/wildlife mirrorless cameras these days.
Z8 and Z9 can do the same, Z9 can do 120fps in jpeg mode 11MP, similar to your Z8. Z8/Z9 will do 30fps in jpeg fullresolution, 20fps in RAW. how long it can do it without slowing down depends on your card, and whether you use uncompressed raw, lossless raw, lossy raw etc
Yes, you are correct. The spec sheet isn't particularly clear on this so I got it wrong taking it at face value, but on the Rolling Shutter Project it shows the sensor readout speed is the limit, which both use the same sensor. For the higher speed continuous (which is only on the Z9 AFAIK, 30fps is the max I see for CH on my Z8) it uses the video pipeline rather than the standard photo pipeline, which is resolution limited and not in RAW. The Z9 /does/ support alternate write mode, however the Z8 only supports split format or overflow with two cards since Z8 is CFExpress + SD and Z9 is 2x CFExpress. I am not sure how this affects write-out speeds but presumably improves it.
Personally I only shoot at 6fps in continuous for birds because anything faster is usually unnecessary (except for hummingbirds) and just creates more exposures to review/delete in post. I generally preference doing quiet single exposure (Qs) when doing wildlife to avoid any sounds, although since switching to the Z8 it's not really an issue since mirrorless is effectively silent in all modes at fairly open apertures.
also, you can do 120fps on your Z8, but it reduces to 11MP, this goes for both Z8 and Z9. It also uses video mode for this, but goes to show sensor readout is not the issue :)
The reason it requires reduction to 11MP and to use the video pipeline instead of the Expeed pipeline is due to sensor readout time. I don't /fully/ understand it, but the sensor readout data on the Rolling Shutter Project shows a Nikon Z8 would max out at ~22fps in full-frame RAW, so no doubt they reduced this to 20fps to give them a margin of error. Reducing to the DX frame size reduces the amount of data required to be read from the sensor, which changes the time it takes to do a readout. The Z8/Z9 are 45MP cameras, so just doing a naive bit of maths, you could expect ~80fps if you applied the same pipeline at the DX frame size, but given that there is already a video pipeline and they needed it to be capable of 120FPS, they already had their answer.
As I understand it, the reason some professional sports photographers don't shoot RAW (or it's less important) is more because they are in an environment where publishing quickly is important, so upload speeds matter and there isn't really much time to postprocess.