Not one of the actions you record require greater than a pruned node. Pruning solely removes historic block information (the total transactions), it does not change the UTXO set comprises (which is maintained individually).
Particularly:
returning all UTXOs for an deal with,
Naively, this may be achieved by way of the scantxoutset RPC, which doesn’t want the total blockchain information. Word that the RPC can (relying on {hardware}) take a couple of minutes by way of go the total UTXO set (no matter whether or not it’s pruned or not).
Alternatively, you should 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 personal keys). It will make the pockets observe all UTXOs (and all transactions even) that have an effect on your stability, no matter pruning or not.
After all, you can even simply join no matter different pockets software program it’s a must 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 already know 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 may have to fill it with this info earlier than with the ability to signal it although, which may be achieved utilizing the utxoupdatepsbt RPC, if not already achieved by your pockets software program (which can usually already know the UTXOs anyway).
That is unaffected by pruning.
validating the spend,
That is essentially the most primary performance of any Bitcoin node software program. It’s unaffected by pruning.
and broadcasting the transaction?
Unaffected by pruning.
