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.
if (!->Unlock(passphrase)) {
                error = Untranslated("Error: Wallet was encrypted but could not be unlocked");
                status = DatabaseStatus::FAILED_ENCRYPT;
                return nullptr;
            }
            
            {
                LOCK(->cs_);
                if (->IsWalletFlagSet(WALLET_FLAG_DESCRIPTORS)) {
                    ->SetupDescriptorScriptPubKeyMans();
                } else {
                    for (auto spk_man : ->GetActiveScriptPubKeyMans()) {
                        if (!spk_man->SetupGeneration()) {
                            error = Untranslated("Unable to generate initial keys");
                            status = DatabaseStatus::FAILED_CREATE;
                            return nullptr;
                        }
                    }
                }
            }
            
            ->Lock();
        }
    }
    AddWallet();
    ->postInitProcess();
    
    UpdateWalletSetting(chain, name, load_on_start, warnings);
    status = DatabaseStatus::SUCCESS;
    return ;