Your approach sounds very reasonable, especially when you start a new project and you are in charge to pick the tools.
In my experience things usually get more complicated for different reasons.
For example, you need to convince your upper management that your chosen tech stack is reasonable enough and visual comparison would help here.
Or you are in the process of migration a big application say from AngularJS to Vue and you can't use Vuex for state-management, because your data should be accessible from both frameworks at the same time. So you need to make a choice from a number of framework agnostic libs.
Or you'd like to switch a library (say from Enzyme to React testing library) and you need to convince other developers. In that case latest ThoughWorks Techradar could help if they put the already used library on Hold.
What also matters to me personally, among other things, is that the considered library should be actively maintained, preferably with a good number of contributors and frequent commits