Launch-Time Proxy Wrappers and Existing Processes
Explain why a process wrapper normally needs to launch the application rather than attaching a proxy to its already-open connections.
A wrapper such as socksify or proxychains normally starts the target program with an interception library. Giving it the PID of an existing process does not retrofit that library into the process or move its open connections. For proxychains-ng, inspect the library-loading requirements of the actual executable.
If the application has native proxy settings, use its documented behavior for applying them. A change may affect new requests while established connections continue on their earlier route.
If launch-time interception is the intended method, arrange an appropriate application restart under that wrapper. Remember that some launchers hand work to an already-running background instance.
A system-level routing or interception design is another mechanism with its own scope. It should not be described as the same operation as adding a proxy setting to one PID.
For a required exit, identify the actual process making new network connections and the route those connections use. A visible process name or a wrapper command in another terminal does not establish either fact.