No. Neither of those will be affected by the remote query timeout setting within SQL server. The timeout of those will be configured within the app's code. Management studio you can change it using the query options (Query menu) or in the login properties when you connect to the server. The VB app will have set it using the command timeout property somewhere in the code (ado). In either case it just applies to the connection that the setting is made on, no others.

The server doesn't know anything about a timeout. A timeout is what the connecting client specifies as the amount of time it is willing to wait for something to complete. SQL does not restrict how long it will run a query for.

The remote query timeout setting is used only when the SQL server that the setting is configured on connects to another database engine and runs a remote query. This is done across a linked server (with 4 part naming or OPENQUERY) or with an ad-hoc remote call OPENROWSET

That's the login and execution timeout, not remote timeout. Remote timeout is set using sp_configure.

exec sp_configure 'remote login timeout (s)'

exec sp_configure 'remote query timeout (s)'

Now, what exactly are you asking about, login timeout, execution timeout or remote timeout? They're three very different things.