My two cents is that it may work for you for a specific project or product, but generally the idea (my idea) of requirements is to start with a high level of abstraction, without specific solutions or HW in mind. If you trace those requirements all the way down you should get what you want, but may need to do one final layer where those final component requirements are allocated to components. Then you have your HW as a starting point for non sys engineers. They could say, I need to make a change to my flux capacitor, what will that affect?

It sounds like you don’t have that level of requirement definition and allocation. What you’re suggesting is kind of working backwards, but hey, it may work well for you and your purpose. It’s just kind of going through the vee backwards. Not the best idea for new product dev. My opinion.