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.
LOCK(cs_);
    SyncTransaction(tx, {CWalletTx::Status::UNCONFIRMED,  0,  {},  0});
    auto it = mapWallet.find(tx->GetHash());
    if (it != mapWallet.end()) {
        it->second.fInMempool = true;
    }
}
void CWallet::transactionRemovedFromMempool(const CTransactionRef& tx, MemPoolRemovalReason reason, uint64_t mempool_sequence) {
    LOCK(cs_);
    auto it = mapWallet.find(tx->GetHash());
    if (it != mapWallet.end()) {
        it->second.fInMempool = false;
    }
    
    
    if (reason == MemPoolRemovalReason::CONFLICT) {