I think you need to understand a bit of some C subcultures to get this reaction. C more than other communities is about best practices to achieve certain goals like portability, stability, security, maintainability, etc. These best practices are often restrictive, or advocate cautious use of language features. Cello breaks a lot of these rules, sometimes haphazardly, and no experienced C person would advocate for some of those hacks.
But what ends up in the HN comment thread is a largely unfamiliar-with-C-culture looks at the README and comes away with the impression that this is an accessible way to learn C, which it is not.
To take an extreme example... If a medical textbook had some strange and nonstandard information, and doctors said it should not be published because it advocates poor health outcomes... Is that "censorship"?
Could it possibly be useful there?
I suspect just using a tiny Lua/JS/Python would be better but maybe in some super niche case this could have a use. Probably not though.
To my knowledge it's been demonstrated on AVR, ARM Cortex-M and ESP32.
It's macro system comes in handy for embedded, too, as you can precompute so much stuff at compile time.