`Rc` freezes the value as long as it's shared unless you use interior mutability. It's fine when you want to share immutable data, but if you ever need to mutate its contents you will have to deal with awkward cases and situations, and at runtime!
Wrapping everything in `Rc` is not a good default strategy. Instead figure out an architecture that works well with the borrow checker! This normally means thinking hard about your data structures and the ownership model of your application.
I love Rust precisely because of this. You can leverage the compiler to drive your development and design. If it's hard, then it's probably wrong!
"I don't understand it, therefore there is something suspicious about it" is a very dangerous way of reasoning.
We burned innocent people because of this not long ago.
Anyways, I find the Bitcoin paper very approachable. You may need to read it a bunch of times until everything clicks into place. But it's all there, in just 8 pages.
If they don't, I'll call it a tragedy.