Two different things get blocked: building the DOM, and painting it.
Parser-blocking. The HTML parser stops for one thing only: a parser-created classic <script> without async, defer or type="module". The parser waits until it has been fetched and run, because the script could call document.write() and change what comes next.
Script-blocking style sheets. A parser-created <link rel="stylesheet"> or <style> whose media matches blocks scripts, not the parser. An inline or parser-blocking script after it waits until the sheet loads, so getComputedStyle() sees its rules; deferred scripts wait too. Since that script blocks the parser, "CSS then script" stalls parsing indirectly.
Render-blocking. HTML treats a document as render-blocked, so it isn't painted, while <body> hasn't started or any render-blocking element is pending, up to an implementation-defined timeout. Render-blocking by default: parser-created style sheets with matching media and parser-blocking scripts in <head>. blocking="render" adds other elements, such as an async script, but only while the parser is still in <head>. Chrome 105+ and Safari 18.2+ support it; Firefox doesn't.
A style sheet whose media doesn't match (media="print" on screen) is neither script- nor render-blocking, though it still downloads.
The preload scanner. While the parser waits, browsers scan the markup ahead and start fetching later style sheets, scripts and images. HTML permits this as speculative HTML parsing but doesn't require it, and it only speeds up downloads; execution order is unchanged.
Rule of thumb: CSS in <head> delays the first paint; classic scripts delay the parser; defer, async and modules delay neither.