The scenario you described which spurred you to suggest this idea is something I would like to comment on.
Compatibility view may be "unreliable". But using IE11 in its native mode(Edge/Standars) and relying on Pega HFixes to force Quirks, etc is even more "unreliable". Each method of emulation has its limitations.
Regarding your second example, SA-13058, https://pdn.pega.com/support-articles/unable-modify-step-activity-rule-ie11, because this is a Support Article, the Topic category derives from the product development backlog that was specified for the parent Support Request (SR), in this case, User Interface. It cannot be changed. If this were a PDN Article, the Topic category could be edited. Who knows? Future refinements to the SA publication process might allow for changes to taxonomy and metadata.
Thanks, Mary. Looking forward to future refinements to the SA publication process that allow for changes to taxonomy and metadata. :-)
As I brought up last March -- while it's intellectually rewarding to have different support articles on the same topic, it is time-consuming for the reader to go through, and some work should be done to synthesize them.