You're assuming that you're starting with an FPGA only project. In reality most projects that are going to be accellerated with these Xeon+FPGA systems is existing software where only a handful of hotspots will have be ported to the limited C language which is significantly less effort than rewriting the entire algorithm in HDL.
It took me a while to grok HDL and write working code (good, maintainable code aside) even though I took digital design courses.
FPGAs don’t get firmware.
HDL is a description of hardware.
HDL can be referred to as code. And I do know what HDL is and what FPGAs are, thank you.
No, it can't. That's why the caps are there and I'm sticking to it. You basically justified it ;)
Code is something that you design to run sequentially. HDL is a description of gates and logic that runs all at the same time.
If you wanted to argue that the bitstream is firmware - that's a tougher discussion.
These (almost by necessity) make you write code that doesn't look like any other C code. You can't just use some pre-existing C library and compile it to use FPGA resources. At that point, why not go a step further and just use a proper HDL?