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.
else if (nLoadWalletRet == DBErrors::TOO_NEW) {
            error = strprintf(_("Error loading %s: Wallet requires newer version of %s"), File, PACKAGE_NAME);
            return nullptr;
        }
        else if (nLoadWalletRet == DBErrors::NEED_REWRITE)
        {
            error = strprintf(_("Wallet needed to be rewritten: restart %s to complete"), PACKAGE_NAME);
            return nullptr;
        }
        else {
            error = strprintf(_("Error loading %s"), File);
            return nullptr;
        }
    }
    if (fFirstRun)
    {
         ensur
        Instance->SetMinVersion(FEATURE_LATEST);
        Instance->AddWalletFlags(_creation_flags);
         Only 
        if (!Instance->IsWalletFlagSet(WALLET_FLAG_DESCRIPTORS)) {
            Instance->SetupLegacyScriptPubKeyMan();
        }
        if ((_creation_flags & WALLET_FLAG_EXTERNAL_SIGNER) || !(_creation_flags & (WALLET_FLAG_DISABLE_PRIVATE_KEYS | WALLET_FLAG_BLANK_WALLET))) {
            LOCK(Instance->cs_);
            if (Instance->IsWalletFlagSet(WALLET_FLAG_DESCRIPTORS)) {
                Instance->SetupDescriptorScriptPubKeyMans();
                 Setup
            } else {
                 Legac