A good start could be a "Down the Rabbit Hole" red section sprinkled through out (like all those side boxes in textbooks and programming books) that emphasises that all of this safety can be negotiated with the compiler through the use of native (implemented in the standard library in Rust) types and links to the relevant chapters in a new window.
For example, when introducing ownership and borrowing rules there could be a quick blurb about RC, RefCell, and other types that let you pick and choose which guarantees you want the compiler to enforce and how "unsafe" is just a keyword to tell the borrow checker to buzz off for a second. Reemphasize it a couple of times in the same chapter and have a small chapter on how to debug corner cases. The point is to plant ideas in the reader, little factoids that may help things click or at least give them a starting point they may remember when they get frustrated by the compiler.
Besides, unwrap() is also terrible in this regard but it's the single most used feature in tutorial code. You need to teach someone Rust before they can learn idiomatic Rust.
The current book has a chapter with a title that's almost literally this: https://doc.rust-lang.org/stable/book/choosing-your-guarante...
I'm talking about scattering bits of that chapter all over the book, including the first concrete language chapter on Variable Bindings. There's over thirty chapters between "Ownership" and "Choosing your Guarantees" which I think creates massive friction for new developers who never even get to that chapter before getting frustrated and giving up.
The "Effective Rust" section of the book is in no particular order; each chapter is self-contained and can be read without the others.
That is one reason why the new book does not have this chapter, though. It's organized differently.
Is there any discussion on the genesis of the new book I can find? I'm curious to see the thought process behind the rewrite.