Use cases are not intended to reflect the structure of a system they are meant to reflect it's behavior.
Does it make any sense to design system this way?
Not really, requirements frequently change. This can result in the class no longer reflecting it's intent.
How it could (positively and negatively) affect design of system with regards of OOP, SOLID principles and domain model etc.?
It doesn't really make sense from an OOP perspective.
Use case titles are meant to describe the whole problem benign solved. this will lead to class names that don't reflect a single responsibility.
Which can lead to all kinds of design flaws (especially down the read).