No, we have no intention of doing this.
A resource is comprised of everything inside the resource directory. You should ignore nothing.
We are, however, likely going to stop writing back an "externally modified" entry to the resource upon scanning it and noticing the signature is incorrect. We'll just let it be wrong in the file and the in-memory / UI representation will still indicate there is a mismatch when necessary.