Not one of the actions you record require greater than a pruned node. Pruning solely removes historic block information (the complete transactions), it would not change the UTXO set comprises (which is maintained individually).
Particularly:
returning all UTXOs for an tackle,
Naively, this may be completed by the scantxoutset RPC, which doesn’t want the complete blockchain information. Notice that the RPC can (relying on {hardware}) take a couple of minutes by go the complete UTXO set (no matter whether or not it’s pruned or not).
Alternatively, you need to use Bitcoin Core’s built-in pockets, and import the addresses or output descriptors for them right into a watch-only pockets (which does not have non-public keys). This can make the pockets monitor all UTXOs (and all transactions even) that have an effect on your stability, no matter pruning or not.
In fact, you may also simply join no matter different pockets software program you need to the node. Relying on what software program that’s, this will likely or is probably not affected by pruning.
offering script info and values wanted to assemble a PSBT,
If you recognize which outputs you wish to spend in a transaction, you may assemble a PSBT for the transaction with none entry to the UTXO set. You will must fill it with this info earlier than having the ability to signal it although, which might be completed utilizing the utxoupdatepsbt RPC, if not already completed by your pockets software program (which is able to usually already know the UTXOs anyway).
That is unaffected by pruning.
validating the spend,
That is probably the most fundamental performance of any Bitcoin node software program. It’s unaffected by pruning.
and broadcasting the transaction?
Unaffected by pruning.
