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.
{
    std::vector<bilingual_str> warnings;
    return RemoveWallet(, load_on_start, warnings);
}
std::vector<std::shared_ptr<CWallet>> GetWallets()
{
    LOCK(cs_s);
    return vps;
}
std::shared_ptr<CWallet> GetWallet(const std::string& name)
{
    LOCK(cs_s);
    for (const std::shared_ptr<CWallet>&  : vps) {
        if (->GetName() == name) return ;
    }
    return nullptr;
}
std::unique_ptr<interfaces::Handler> HandleLoadWallet(LoadWalletFn load_)