Not the idea. The idea is correct and also should be everyone's job in the engineering org
Do we have a Cares About Internal Comms Engineer? A Remembers Why We Did It This Way Engineer?
Mostly the title means whatever it means at your specific company, which is true of most titles. What is a product manager? What is a responsible engineer? Are the others NOT? What the actual heck is a growth engineer as distinct from marketing? You can play this game all day and the answer is always depends, ask their manager and maybe (usually) they also do not know.
The funny part is the guy who invented most of this thinking would hate what we did with it!!!! Stafford Beer's whole thing was that it's recursive. Every team needs the function that looks up and out, not just the org. Every team! Donella Meadows put it a different way, that adding a box to the chart is one of the weakest moves available to you and changing what everyone believes is one of the strongest. We looked at both of those and hired a guy.
Which makes it an accountability sink (YUCK). Somebody noticed nobody was thinking about the whole thing, correctly clocked that as bad, and then solved it by making it one person's job. Guess that means it's not my problem!!
I have never once been on a team where the systems engineer was the only person who needed to be doing that, but I have met a lot of good "systems engineers".