Hi,
Pardon my confusion here, but are you saying that you want lintian to no longer emit this error message, or are you saying that you are interested in churning through and doing all the fixes for font packages that throw it? (That question may just be me getting hung up on the wording.)
I do agree that upstream is the best place to fix these, certainly. As for the next-best option, I wonder if there might be some concern with blanket rewriting that entry in the [OS/2] table. For example, I think that might be considered a functional alteration, which would trigger renaming under OFL-with-RFN conditions.
Nate