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_);
    
    
    
    
    m_last_block_processed_height = height - 1;
    m_last_block_processed = block.hashPrevBlock;
    for (const CTransactionRef& ptx : block.vtx) {
        SyncTransaction(ptx, {CWalletTx::Status::UNCONFIRMED,  0,  {},  0});
    }
}
void CWallet::updatedBlockTip()
{
    m_best_block_time = GetTime();
}
void CWallet::BlockUntilSyncedToCurrentChain() const {
    AssertLockNotHeld(cs_);
    
    
    
    
    uint256 last_block_hash = WITH_LOCK(cs_, return m_last_block_processed);
    chain().waitForNotificationsIfTipChanged(last_block_hash);
}
isminetype CWallet::IsMine(const CTxIn &txin) const