Hierarchical backup trees

Consider how you can trick ATI to make backup generations (for instance with chain2gen) by simply moving files into subfolders.

For instance, if you remove the last incremental backup, Acronis will not care and just make a new one relative to the LAST one it finds.

So, I had an idea: hierarchical backup trees. Consider one full backup as starting point. Now you make 5 incremental backups and then you move those into a subfolder and let Acronis run again.

You essentially end up with a differential backup that depends on the original full backup. This could technically be done recursively and with any kind of nesting.

You might end up with something like this:

The square denotes a full backup and the other shapes represent incremental backups.
The numbers only show the order of backups. It's also chronological from left to right. Arrows show dependencies.

What you could do with this:
You can keep a lot of small backups while only relying on very few to stay in tact. Consider somebody who makes 30 incremental backups in a row in order to save space. Instead, only 5 incremental ones could be done at a time with the first file in the series always directly relating to the original backup. It would require a bit more space, but yield much better reliability.

Would you agree that this is whacked considering that we are talking about our dearest BACKUPS and not just some research project? I mean, delete the wrong file in your nested folder structure, and you're toast. Also, recovering requires moving files around because a subfolder might only contain incremental backups, but not the original reference.

Comments?