I understand the logic in that from a technical aspect in the workflow of saving layout changes (and being able to cancel those if required), but from an end-user experience point it is not that great. So...
Edit a layout, then edit a custom block and change its text. Save the block (it feels funny by the way that the button says "Save configuration", but lets leave that for another issue*). At this point, a new user would expect that refreshing the page that shows the changes they've just made in the backend would reflect those changes in the front end. That doesn't happen though. They need to return to the layout edit page (thinking that Backdrop "doesn't work") and then they see the "This form has unsaved changes." message that asks them to save the layout (#1656).
As I said, not optimal UX there.
Recent comments
It's not difficult to write JS code in an admin theme (without a module) that would save text from CKEditor to LocalStorage every X minutes and add a button to restore the text from LocalStorage...
Implementing autosave in Ckeditor 5
Another contrib module came to my mind: Save & Edit. Of course, that's also not what you had in mind - it saves to the server. But it can be helpful when the network the author's...
Implementing autosave in Ckeditor 5
... Autosave module that you mentioned, but it saves to the database I thought, that's what you're after. I am looking for is to save to localStorage...
Implementing autosave in Ckeditor 5