Passing some redundant parameters to an interface vs creating a new request object every time for the interface
Since what you want is a total transparency on how you access the propertyA then solution 1 seems better. Because with solution 2 you have to change the request object.

You should clearly identify your parameters. Some may be changing the output that is needed, other may be more related to the underlying service and can be "defaulted" into the dedicated proxy. At the end if you still have some unused parameters, this is acceptbale until the response is still correct.

It is not because the serviceB has a functionnality (param3) that you are obliged to use it. Your services should have a common behavior if you want to exchange them without any impacts.