<p>I agree with using a historical lock for the case you've described. It's... kind of exactly the situation the historical lock was invented to handle.</p>

<p><em>(Terminology note: in this post, when I talk about locks, I'm referring to historical locks only. What I say may not apply to the other kinds of locks we have, like the temporary kind of lock used on posts where comment threads are devolving into unproductive personal attacks.)</em></p>

<p>At first glance, a lock might seem like a "super-close", but locking and closing are different animals. A locked post is like a museum exhibit: frozen in time and unchangeable, something to just goggle at for a moment before moving on. A closed post is more "alive"; the only thing that can't be done there is adding new answers. More relevant to this situation, the close state carries the implicit message "please improve this question so that it can be reopened." It doesn't send that "this is permanently bad" signal. And it's relatively easy for a few people to quietly reopen it. For more info, see the network meta's community-generated FAQs on <a href="https://meta.stackexchange.com/questions/10582/what-is-a-closed-on-hold-or-duplicate-question">closing</a>, <a href="https://meta.stackexchange.com/questions/22228/what-is-a-locked-post">general locking</a> and <a href="https://meta.stackexchange.com/questions/126587/what-is-a-historical-lock-and-what-is-it-used-for">historical locking</a>.</p>

<p>As for your concerns:</p>

<blockquote>
  <p>It can only be done via flagging, i.e. community cannot take care of locking without mods.</p>
</blockquote>

<p>Locking is a pretty severe action. It should be used only rarely, and in exceptional cases. (I'm using the programmer's definition of "exception" there, meaning somewhere between unusual, non-standard, unexpected and slightly problematic.) We require a mod's intervention to make extra sure that locks are only applied to posts that deserve it. The actual process isn't hard or time-consuming, the mod's role there is really just oversight.</p>

<blockquote>
  <p>Similarly, it can only be undone via flagging, i.e. community cannot reverse a wrong decision without mods.</p>
</blockquote>

<p>For something as disruptive as locking, we didn't want people to get into fights the way we've seen "close/reopen wars" in the past. And as rare as locking is intended to be, <em>un</em>-locking should be a dang unicorn. This is because locking shouldn't have happened in the first place for a post that didn't deserve it or wasn't going to stay locked. So, again, we want mod oversight before a change in lock status is made.</p>

<blockquote>
  <p>When a thread is locked, it's not possible to edit any answers, post new comments, or even vote on them. I.e. if there is a mistake in one of the answers, it's there forever, and one cannot even comment to point it out. Note that sometimes we are talking about very visible threads with large number of views.</p>
</blockquote>

<p>This is an annoying side effect, to be sure. When it comes up, it can be a sign of an error in process. Locking isn't supposed to be anyone's first choice of action when thinking about how to handle a post. In many cases, <strong>especially</strong> in the case of incorrect information, it may be better to delete a post outright than put a historical lock on it. This is the sort of thing should be considered and discussed <strong>before</strong> a decision is made to lock a given post.</p>

<blockquote>
  <p>The displayed message says that the thread is locked "for historical significance", but often there is no particular significance.</p>
</blockquote>

<p>Well... don't do that, then. Lock those posts that actually have historical significance, and do something else (close, delete, ignore) with the others.</p>
