I'm afraid that is not the conclusion I draw from the snippet you posted.
It's very clear to me that the HLL under question at that time prevented the programmer from performing the low-level optimisations that the C programmer could optionally do. The debate appeared to be be whether to let the language exclusively optimise the code, or just do no optimisation and let the programmer do it.
This is why the sentence ": Oh, yeah. That would have been fine. And, in fact, you need to have something like that, something where experts can really fine-tune without big bottlenecks because those are key problems to solve. " is in there - it's because the HLL languages literally wouldn't let the programmer optimise at the level that C would let the programmer optimise.
Honestly, if the proponent for the HLL language didn't add in "Use the HLL, but not for OS and low-level code where you really need to fine-tune", you'd have a point, but they said it, and so you don't.
Inline Assembly isn't C.
What page of C standard describes it?
As for the rest of your comment, unless you are using a PDP-11, you will be surprised.
Had you been clever, you would have pointed out that inline Assembly is defined in the ANSI C++ standard, with the mention of asm (content) language construct, leaving the meaning of content implementation defined.
As it is also defined in the Ada language standard, Modula-2 standard revision, and Oakwood Guidelines for Oberon-2 implementation.
That is the thing mixing up C with compiler specific features, confusing the language for its standard and assuming no other language in the planet offers similar capabilities.
C is not defined by or constrained to the standard. It predates it and every implementation extends it, as is intended by the standard.
The person confusing the standard with the language is you.
Page 514 (of version n1256) of the ISO C Standard
Moving target, to be, sure, but it's been there for 20+ years now.
Annex J.5.10 The asm keyword
to quote a stack overflow answer (that sounds a lot like an answer commonly given back in the day on Usenet and #C IRC channels)
informative, not normative, so an implementation need not provide inline assembly, and if it does it's not prescribed in which form. But it's a widespread extension, though not portable since compilers do indeed implement it differently.
https://www.open-std.org/JTC1/SC22/WG14/
Optimization taking advantage of UB had to be introduced during the 1990's to make it into a reality.
Until the widespread of 32 bit hardware, even junior Assembly devs could relatively easy outperform C compilers.
Which is what the interview is about, originally C lacked the optimization tools, relying on developers, with tons of inline Assembly.