Because I had come across this feature recently in one of my engagements, so I will try to provide some PoV here (as providing it in comment is not an option).
First things first - This feature is still in Beta, so choose carefully.
If you are looking from a Release Management perspective, there's no impact as such. If you read the below from the documentation for Cloning feature it mentions that its a feature to allow users work in parallel and expedite the sandbox creation process altogether.
Save time by customizing a sandbox with a set of data and metadata and then replicating it. Sandbox cloning simplifies having multiple concurrent streams of work in your application life cycle. You can set up a sandbox for each type of work, such as development, testing, and staging. Your colleagues can easily clone individual sandboxes instead of sharing one sandbox and avoid stepping on each other’s toes.
Personally, I won't recommend to clone a sandbox for your Release Management when you want to move your code from say DEV to QA or any higher test environments. One of the primary reasons is that DEV is always a working copy and that when you Clone a sandbox from it, it will end up having some untested features being moved to a higher environment.
This feature can save your time, say if you want another developer or say another tester test out in parallel without impacting your "active" dev/qa environment, that's where this feature will be helpful. In that case, you don't need to refresh a new sandbox from scratch from Production, rather just "replicate" the one which you want to test out. And with this, you are also getting a set of data that was created in the source sandbox so that you don't have to recreate any data out there.
If you are looking for a robust Release Management, always go through the route of a "source of truth" using a "Version Control System", so that you don't have to rely on any sandbox but a repository where you have all your metadata in there.