IDisposableAnalyzers VS Microsoft.Unity.Analyzers

IDisposableAnalyzers: object disposal validation

Sure, but I am the opinion it does compose, if one embraces it isn't the same as writing C++ in C#, not trying to downplay your experience on the matter.

For example, here are the Roslyn analysers for a more RAII like experience with IDisposable,

https://github.com/DotNetAnalyzers/IDisposableAnalyzers

Turn "DISP004-Don't ignore created IDisposable." into a compiler error and you have your region allocated RAII like experience.

And moving a bit the goal posts, for those scenarios where C# fails completly to provide a usefull solution, we can rewrite just that module into C++ (preferably C++/CLI when only Windows matters), and have the best of both languages.

Unity Analyzers: to find gotchas in Unity-based games and apps.

That warning is suppressed by USP0003 in the Microsoft Unity Analysers. In Visual Studio Community they should be installed by the Game Development with Unity package. I'm not sure about Visual Studio Code though.

My understanding is that SetPositionAndRotation is just a shorthand for setting position and rotation on 2 lines. However there are posts that suggest there is some performance benefits.

Don't compare tags like this if (collision.gameObject.tag == "Platform") because it's inefficient: https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0002.md

You can use either regular Visual Studio (including Community Edition) or Visual Studio Code as your editor. I usually prefer the full Visual Studio because I work with other types of projects, it provides good refactoring support and there are some good analyzers available.