Re: So... is he an engineer?
I think you accidentally make a better point - you can call yourself a "chartered engineer" as a distinction, for the purposes of the articles' point about protecting big infrastructure projects.
The term engineer on its own covers a multitude of possible skills (or lack of) and requires some context.
What about people called a "software engineer" for example, a broad interpretation will have all sorts of unintended consequences, while adding no value to the state at all.
Using terms like, chartered, certified, registered etc should be what the state checks, not just the generic terms.