Hey @Siegfried, good to see you here! And thank you for your report.
We got several reports of similar behavior in VSCode and we are planning a fix to at least make sure that the Node-related popup only shows when there is an actual issue with Node 
.
We know that the resolution of tsconfig.json can be problematic in some cases. As suggested in this other thread, maybe you can use the sonar.typescript.tsconfigPath property in Settings > Tools > SonarLint > Project Settings > Analysis properties, to force the TS analyzer to use the right one for your project(s).