Ask who really needs Rust. People who write code that has to work and causes real trouble when it doesn't. That includes embedded system programmers. They're typically into C and can use an oscilloscope. They seldom know C++ and have never heard of Haskell. But they can lay out a circuit board and get it to work.
Rust needs to be accessible to those people.
You just need to know how closures work at a high level, which is pretty straightforward. Rust closures are basically the same as C++ closures.
If you're really worried about the generated code generally iterator code with closures compiles down to the same thing as the imperative code. This isn't a hidden complexity unique to Rust; C code these days is pretty far removed from the generated asm too.
An example: https://www.reddit.com/r/rust/comments/5iwyt9/how_to_accompl...
You might not need to know what "vtable" means, but the differences between, for example, `T: Fn()` and `T = Fn()` are pretty important.
https://doc.rust-lang.org/book/closures.html
https://doc.rust-lang.org/book/trait-objects.html
Basically, a closure is just an anonymous trait, and traits are implemented with vtables. This reminds me of how you can think of Java's lambdas as anonymous classes (though they're not implemented that way).