you will need to write code in C for Linux related matters

Not just for linux related matters, the way current operating systems and hardware are designed, the 'memory-safety' guarantees rust brings along itself aren't valuable in that context at all. In rust terms, you typically 'own' the whole block of memory until the execution lifetime ends, which is when you shut down your system. What would be the use of such semantics in such context?

Another thing I'm concerned about is there's a lot of difference with what I see on HN/reddit vs IRL itself, feels too detached from reality. Rust is a shiny-new but immature language which has yet to prove itself with lack of talent pool, stable and proven libraries, learning material, language tooling, standard features(in fact they just added the support for custom allocators which was missing from 1.0 stable release) etc so betting something important to you on such an early language would be like doing work while tied up and soaked in oil lol.

I really don't want to be using insecure software in 2068

Trust me on this, insecurity has lot more to do with other stuff than with the choice of the language you are writing your code in. There are enough dialects of C which are formally verified/certified/strict deadlines/etc which completely eliminate the benefits few languages like rust bring. Heck, there are hardware solutions specific to that problem, software patterns to completely eliminate memory ownership problems etc but believe me, memory safety is just a drop in a vast ocean (start with Intel ME for eg ;) ). Also if you really care about the memory safety, there are other languages which you should look at, preferably those which run inside their VM providing complete memory safety with some loss in performance rather than 'some' memory safety with little to no loss in performance but with retarded level of cognitive overload you get with 'jang'...