What I am describing here is something of a Kludge, but requires only FileMaker Pro Advanced to pull off.
You Might be able to set up a clone FileMaker file (no records) with an import records script in it. You could then pull up the records you want to export and then, from your main file, perform the import script in the clone file to import the found set of records you have just pulled up into the clone. Since this is a fileMaker file it can be password protected. FileMaker can even make copies of such a clone file (to keep a clone on hand for the next export) by inserting the File into a container field and then using export Field contents to make copies of it. This "file shuffle" can be pulled off only if you do it in just the right sequence but a single script can step through the entire process, including sending an email with the fileMaker file attached.
If your clone file is "bound" to a runtime solution (this is the part that requires FileMaker advanced), your recipients need only have the Runtime package on their system. They take the file you email to them and drop it into the run time folder to replace the copy already in the folder, then launch the runtime to open the file so that a script in the runtime can export the excel file if that is the file format that they need.