1. IMHO, that would be crazy as you haven't a clue what a suspect file might do, it could installs rootkit to hide malware from your AV. So disabling the AV running the file and then deleting it and scanning would be worthless in this example.
There is truly only one way to see if a detection is an FP and that is by analysis and not what you suggest. You can google the file name and see if there are any associations with malware, you can check here, in the Viruses and Worms forum, giving the file name, location and malware name of the detection.
You check the offending/suspect file at:
VirusTotal - Multi engine on-line virus scanner and
report the findings here. You can't do this with the file securely in the chest, you need to extract it to a temporary (not original) location first, etc.
2. They are different in that the local drives scans all hard disks/partitions/folders/files, the folder select only those that you actually select for scanning. If you put a check mark against all drives using the folder select option, then it would be the same, but that is a long way round, rather than select Local Disks.
3. Before an on-demand scan the memory will be scanned before the Simple User Interface, but it doesn't scan the registry. The only time it would go to the registry is if a spyware detection is made that it would try to find associated registry entries for the file. avast also does an anti-rootkit scan at the satrt of the on-demand scan, if the sensitivity is on Standard or Thorough.
4. It is quite possible that yes it would run on x64 OSes as that OS allows 32bit code to run and many of the applications installed on it are 32bit applications (avast is a 32bit program but is able to run on 64bit OSes, it uses different drivers though). The only deterrent would be that 64bit OSes are supposed to be tighter on security so may limit the potential, but it is possible, but not certain.