Re the deletion question, no - because there's no such thing as a 'negative file'. Your full backup has a copy of \Inbound\somefile.TGA and a Restore from the Full location will copy that to E
The Incremental has a copy of Outbound\somefile.TGA and will Restore that. But there's nothing stored in the Incremental location to say \Inbound\somefile.TGA is now deleted (not present) on Source. All that happens is that a fresh copy of \Inbound\somefile.TGA isn't present in that Incremental location, but that isn't necessarily because it was deleted (could be it wasn't re-copied because it hadn't changed). There's nothing stored in the Incremental location to say 'delete \Inbound\somefile.TGA' or '\Inbound\somefile.TGA was deleted' - it just contains files that are new or changed since previous run.
If you have a Mirror Right profile (run in Restore mode, i.e. backwards) that you point at an Incremental backup on I (which by definition only incorporates a sub-set of the whole file-set) it will want to delete ALL files on E that the Incremental location doesn't contain (which is why we suggest in the Restore wizard that you click Yes to skip such files). You thus can't leverage the fact that that Incremental location doesn't contain \Inbound\somefile.TGA to delete \Inbound\somefile.TGA on E drive without it proposing to delete everything else from E that isn't in that location either.
This is a basic Catch-22 re deletions (or remaining detritus c/o Moves) of Incremental backups in general (not just in SB), which is why it's wise not to wait too long between Full backups, to avoid such files building up.
Re folders, check Decisions-Files > Folders. Note that as per the contextual Help on the Folders page, this settings page refers to empty folders (or, folders from which nothing is copied c/o filtering, etc). Folders containing files that are copied are obviously created (as somewhere to put the files) so these rules don't apply in that case.
The Incremental has a copy of Outbound\somefile.TGA and will Restore that. But there's nothing stored in the Incremental location to say \Inbound\somefile.TGA is now deleted (not present) on Source. All that happens is that a fresh copy of \Inbound\somefile.TGA isn't present in that Incremental location, but that isn't necessarily because it was deleted (could be it wasn't re-copied because it hadn't changed). There's nothing stored in the Incremental location to say 'delete \Inbound\somefile.TGA' or '\Inbound\somefile.TGA was deleted' - it just contains files that are new or changed since previous run.
If you have a Mirror Right profile (run in Restore mode, i.e. backwards) that you point at an Incremental backup on I (which by definition only incorporates a sub-set of the whole file-set) it will want to delete ALL files on E that the Incremental location doesn't contain (which is why we suggest in the Restore wizard that you click Yes to skip such files). You thus can't leverage the fact that that Incremental location doesn't contain \Inbound\somefile.TGA to delete \Inbound\somefile.TGA on E drive without it proposing to delete everything else from E that isn't in that location either.
This is a basic Catch-22 re deletions (or remaining detritus c/o Moves) of Incremental backups in general (not just in SB), which is why it's wise not to wait too long between Full backups, to avoid such files building up.
Re folders, check Decisions-Files > Folders. Note that as per the contextual Help on the Folders page, this settings page refers to empty folders (or, folders from which nothing is copied c/o filtering, etc). Folders containing files that are copied are obviously created (as somewhere to put the files) so these rules don't apply in that case.