The two issue are described as following in the User Guide, Chapter on Change Management for Oracle Applications | Section on Scheduling Patch applications and impact analysis
6 (Optional) Deselect Ignore Restart File.
If this option is deselected, Stat will fail the request if the AutoPatch utility identifies restart files for a different patch.
Unless you deselect this option, Stat will always continue processing a patch if restart files exist for it.
Meaning, for the same patch, no, you can’t change the answer. It will always attempt to restart. Unless you remove the restart files from the environment.
For question about the adpatch parameter, see the same guide, but look at the Patch Management section under Defining Patches:
After you upload a patch and save it to the Stat Repository, Stat populates the New Oracle App Patch window with the values it has read in the patch zip file,
including prerequisites and drivers.
However, you can specify additional information as needed. This is done on the General tab.
The General tab allows you to edit many of the same values you can view from the Patch Inventory tab on the Oracle Management Console.
On the General tab you can also specify AutoPatch options which are additional default parameters passed to the AutoPatch command line during the patch apply process (users can override these parameters at runtime).
The syntax for Autopatch options is name=value pairs separated by spaces.
Refer to your Oracle documentation for a list of valid AutoPatch command line options.
Keep in mind that Stat calls adpatch and adpatch creates the log files and the restart files.
If you are going to ignore the restart files and it isn't happening, then remove the restart files from the folder
(save a copy somewhere just in case) and try to apply the patch again