Your assumption that “using reflection means the code is wrong” seems a bit extreme, at least in .Net. Every time you interact with types, you use reflection. Xml and Json serialization/deserialization uses reflection, and also Entity Framework. If you use mocking in test you are using reflection.

We have an excel export functionality on our sites that uses reflection because we can write 1 function and export any types we want, thanks to reflection.

That's why live services games needs to incorporate micro transactions. The studio needs to have a constant revenue stream to maintain the development and the infrastructure cost.

That's why live services game needs to end