SET DATABASE PRM(Min TLS Version) and Preemptive Procs

17R5

So, I currently have a method where I do

SET DATABASE PARAMETER(Min TLS version;1)
`CALL A WEB SERVICE
SET DATABASE PARAMETER(Min TLS version;3)

Now I’m considering re-writing this: to of spawning my -CALL A WEB SERVICE- into a preemptive worker process. like this:
SET DATABASE PARAMETER(Min TLS version;1)
Call a worker process to CALL A WEB SERVICE repeat: wait for a response, until Response is received
SET DATABASE PARAMETER(Min TLS version;3)

QUESTION #1:
The Scope of SET DATABASE PARAMETER(Min TLS version;1) ~seems~ to indicate that it is database wide - which should include preemptive processes: is this correct?

I wish there was a way to set Min TLS version per process: this would make much more sense: as when calling external Web Services: I’m limited by the remote technology: and my database connects to many different remote technologies: each one of them can be different.

Your request (set the minimum TLS version for each HTTP client request)

but SET DATABASE PARAMETER is a thread-unsafe command by design,

and the selector Min TLS version applies to both server and client,

so I think the request calls for a different kind of implementation.

there will probably be a performance penalty to not share the same TLS context across all processes.