I haven't seen a link budget. Do you have a link for one about the "likely error rates"?
My guess is Starlink is going to need FEC for Doppler effects and multipath in urban environments. Maybe they will be able to overcome multipath with modulation. But Doppler shift will be significant with LEO.
The latest 802.11n standards have been increasing physical layer frame sizes, not decreasing them. I don't know of any modern wireless standard that doesn't use FEC. Coding gain is significant in most link budgets I have seen.
The last satellite RF downlink I worked with was for JPSS-1 in LEO nearly 6 years ago. There was a (255, 223) Reed-Solomon code with an interleave depth of 4 frames. So you effectively had to receive 1024 bytes, decode, and you got 4x 223 bytes worth of information. While latency wasn't a major concern, this scheme seemed pretty standard to me. If you don't believe me, the spec is public information:
https://www.star.nesdis.noaa.gov/jpss/documents/CDFCB/GSFC_4...
I'm sure SpaceX is trying really hard to control latency - so it doesn't get out of hand! One set of RF processing here, another over there, each with their own filters and decoding algorithms and then you have an extra 100 ms of delay in the system.