Ah, I wasn’t really suggesting that the (contents of the) clipboard be immediately serialized to disk, but rather that an OS built-in clipboard manager be created that exposes its contents as shell objects living on the shell Desktop (rather than the filesystem Desktop.) So every cut would put a shell object onto the shell desktop, but this would just be a handle to a memory object living in the clipboard manager. Pasting would move that object from the shell Desktop, to the shell Trash, such that emptying the Trash would get rid of it; but it wouldn’t really be “in” the filesystem Trash either.
If you select and copied the shell object on the shell Desktop, you’d just be making the “selected” clipboard handle the one referenced by the shell object.
If you moved the shell object, you’d be instantiating a physical filesystem .scrap object at the destination.
And, of course, since all this is simulating something persistent, you’d expect the clipboard manager to make each clipboard object refcounted, and not get rid of objects as long as something (e.g. a shell object) holds a reference to them; even meaning that the clipboard objects with nonzero reference-counts would need to be persisted to an OS “clipboard database” on shutdown, such that the shell objects referencing them would still be valid on next startup.