This is a proposed change that not going to happen soon, but I think it is worth moving in the direction in a major release.
Our bsconfig.json format is more flexible than JSON spec, i.e, it allows comments and trailing commas. It is indeed more convenient for users, so why not when I introduced bsconfig.json in the beginning?
At the same time, I learned lots of things in the last few years. In general, I believe it is a good tradeoff when exchanging some user convenience for easy/solid tooling. Having it standard compilant means you can query such data in your favorite programming language without any third party deps, it makes tooling easier.
Easy, just ensure your bsconfig.json is indeed a valid json format, this can be checked using your favorite editor, e.g vscode.