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.
The game was not great, at least personally. It wasn't bad, but it was just BL3 in a different dress, with less interesting story, less interesting characters. Also the DLCs were insane cashgrabs, not even close to the value BL3 DLCs had.