I believe most kernel developers would recognize how many kernel bugs have been introduced because of their choice of language - C. These are the best C programmers in the world probably and yet their code still suffers from buffer overflows, double frees, ownership issues etc.
So that is basically why Rust is generating interest - it is a compiled language and it links with C quite easily. It's also a more modern language than C, the compiler is very strict but helpful, the language is terse, it doesn't require code be split into headers / sources, it has inline markdown documentation, inline tests, and it is safe by default. Safe by default means that any nasty, volatile code can be encapsulated in helper functions where the unsafe portion is called and the surrounding code which is safe by default benefits from additional compile time checks. In addition since its a modern language, better patterns can be supported, e.g. streaming IO through lambdas rather than exposing buffers to functions and so on.
I do think some of the objections are valid. Rust is self describing for example. It would be good to separate the language from the implementation. I also expect that many kernel devs just find it intimidating as a thing because they're so used to C, particularly GNU C with a bunch of extensions. But I think the fundamentals of Rust aren't that far removed from C - it's a C like syntax and compiles into .o files but I imagine a lot of the concepts of the language / std library on top and the strictness of the compiler are things that some people would need to adjust to.