Been like this since pre MSFS 2020 release, where the pre-release Model was not encrypted.
Surely, this can be fixed by asobo, as it cannot be fixed by 3PD, as it is now in an encrypted Model
The use of a / is a direct violation of the SDK, which is all fairness, may still not document that the / is an invalid character in a Node name …, so at a minimum, the SDK needs an update
Just replacing the / with a _ would easily fix it in the C172 Classic