Number of .qmail-qconfirm files

I am curious about one of the design decisions for qconfirm, and have a 
proposal to change it.

qconfirm's actions depend on creating (potentially) multitudes of
ephemeral .qmail files in a user's home directory.  Depending on the file
system and OS in use, this can lead to performance issues whenever the
home directory is searched - which is likely to be fairly often. This also
precludes using qconfirm in a situation where the home directory is
read-only. And finally, it means that the bounce message for a reply to a
no-longer-valid qconfirm confirmation request will be a vanilla qmail
bounce, rather than a "that cookie is no longer valid message" from
qconfirm.

As an alternative design, I'm considering having a cookies subdir which 
contains a symlink to the message file in the pending directory. We can 
then have only one .qmail file, .qmail-qconfirm-default containing:

|qconfirm $(readlink .qconfirm/cookies/$EXT) ./qconfirm

(or we would modify qconfirm so that it did the readlink itself, and 
replied politely if the readlink failed).

Is this a crazy idea? Have I missed something?

---
Charlie