Would it be completely unreasonable to allow `fundrawtransaction` to use unsafe outputs?

I understand this means the resulting transaction may be invalidated whenever the unsafe output I'm relying one disappears (e.g. because the transaction that produced it was RBF-ed) but in my case that's ok, I'll react to that and re-publish the tree of child transactions accordingly.

But let me know if you think that's too much of a footgun for users, in that case I'll architect my solution differently.
#include <.h>
#include <chain.h>
#include <consensusconsensus.h>
#include <consensusvalidation.h>
#include <fs.h>
#include <interfaceschain.h>
#include <interfaces.h>
#include <key.h>
#include <key_io.h>
#include <outputtype.h>
#include <policyfees.h>
#include <policypolicy.h>
#include <primitivesblock.h>
#include <primitivestransaction.h>
#include <psbt.h>
#include <scriptdescriptor.h>
#include <scriptscript.h>
#include <scriptsigningprovider.h>
#include <txmempool.h>
#include <utilbip32.h>
#include <utilcheck.h>
#include <utilerror.h>
#include <utilfees.h>
#include <utilmoneystr.h>
#include <utilrbf.h>
#include <utilstring.h>
#include <utiltranslation.h>
#include <coincontrol.h>