I’m not sure, I never used mdbook configuration/customization much myself. Judging from documentation I could find online, this might not have a top-level configuration, except perhaps the (presumably overkill) solution of writing a whole preprocessor just for this. But of course, someone else might know more/better
I think that the documentation states that one need to do both – enable the feature in the first place in the config, and tag each code block that should be editable with that attribute.
You are right, I checked it locally. Was this immediately clear to you? I read the first paragraph as "make all code blocks editable", rather than "enable the feature so that the editable marker on code blocks works". Might be just me, but if not, maybe the wording of the paragraph could be improved.
No, not immediately clear; though after re-reading it once, that’s what I did understand from it. I too think the wording of the documentation can be improved here.