It is possible; though we need a good proof of concept here in the community

. I’m actually working on a site now that will have both a traditional MODx interface, and an alternate complete Flash site (from a template monster template actually); in this case, I’ll provide the QuickEdit module on the traditional pages and then most likely, create alternate dynamic XML page that pulls in the content from a requested page (along with any other important data I might want in the Flash movie; like logged-in user data, etc). Not being familiar with using XML inside of Flash though, it may take me a while to work this out, so feel free to share anything you do accomplish in making this work (it’d help me out greatly, at least

).
As for your question regarding QuickEdit module id of a page -- I’m not sure I am clear on what you are asking, but every page has an ID, and the QuickEdit plugin component uses the current page ID to determine what editor features to present on the front end when viewing that page. Does this help?
On a related note, I wonder if we could find a way to provide native MODx data as XML content to Flash and AJAX components from the same MODx facility...just thinking out loud...seems like the requests/responses could be handled by Javascript and Flash in a similar manner, but again, my Flash knowledge is limited.