This is going to be a long post that will "potentially" give you an idea about many things -- but not make folks happy. So here goes:
"The Apple Way" -- this is the way in which Apple recommends to developers to create Apps and WHERE to store various "parts" and what NAMES to use with them. I haven't been a "develper' now since pre-Tiger, so much of what I"m puting forth is based on assorted conversations with active developers and the like.
Also, keep in mind these comments are very general and not particularly technical.
I cannot tell you exactly what "things" are supposed to be in what files, just the structure. Apple wants all developers to use the "Domain style" name for identifiying "things' which belong to specific applications and developers. It is actually quite simple to understand.
"Lock" files are exactly that -- they represent a mechanism by which an application can identify that it is "in use" and typically contains a "pid" -- program id.
Most?Many?All? Apple applications (like preview) are "robust" -- that is to say, if they go to access a file (like a plist) and that file does not exist, the application will create it "fresh" using some set of parameters hard-coded into the application. It's kind of a "fail-safe" mechanism. If you find you need something in a parameter (plist) file and it is undefined because the file does not exist - don't crash, simply use a pre-defined default and create the file new.
Part of all of this relates to how and were "apps" store information in the file system. User related apps are supposed to store information in the User's Library directory; while system relatd apps use the System Library directory. There are many apps, especially those ported from Windows, Linux, Unix or other non OSX environments.
=====
Now an important thing about OSX Mavericks. Apple, like many other vendors (including Microsoft) ASSUME that you have a HIGH SPEED connection to the Internet active AT ALL TIMES when you are trying to use OSX.
I have not put up WireShark or similar, but if I could, I would undoubtedly see that in that first 15-90 seconds at strartup, OSX and various individual Apps are communicating (one might call it syncing) with iCloud -- even if you don't have it configured. If you have it configured, some things will happen quickly; if you don't things wind up waiting for "time-outs."
"Time-outs" are problematic. If you optimize them based on Cable Modem Speeds (20meg bits per second) a request made will be answered very quickly. But ii that request is made over a DSL line (2meg bits per second) that timer will expire and require a "retry'.
On top of this, there is a little discussed concept in Networking -- "Guaranteed MINIMUM response time." This means that if two users one on a FAST link and one on a SLOW link perform the same action at exactly the same time, INSTEAD of the fast link getting done quicker than the slow link -- both links take the same amount of time to complete. This is part of the concept of "engineering expectations."
Those of us who are used to HIGH-PERFORMANCE desktop computers EXPECT certain levels of fast response to our keystrokes. Other folks either "don't know any better." Or have "learned" to "live with certain characteristics." Yes, this is serious social engineering. This issue is quite common to MMOs.
So, not only do we find the OS itself "syncing" with the iCloud for various reasons, but so do individual apps. AND we have the comparison between OSX on a desktop, and IOS on various generations of iPhone and iPads.
Then last of my comments -- Mavericks has a new memory management scheme. Many different "speed-ups" in OSX and in IOS are accomplished by "pre-loading." These "pre-loads" are particularly "speedy" for folks who "open-up" (note, I did not say power-up) their lap-tops and go to Mail and Safari and then close their laptops (note I did not say power-off). By not powering down, the "state" of your computer is retained for the next time you use it... a FAST recovery. But if you shut your system down and DO NOT save all those pages you had open in Safari and all those apps you had open; when you next power-up your system, you have to "pre-load" Mail and Safari BACK into memory. I hope you can see the pattern here. You have to take a BIG step back and pay attention to some serious Computer Science theory here to understand what is happening and why things seem a bit unpredictable. And all of this sort of thing relates to the speed of you disk drives, etc. Computers are "Systems." Their individual components interact with each other and all contribute to the final display on your screen.
There ARE issues with Mavericks; Spotlight takes "forever" to index disks and while it is running, response to other things, especially any activity which utilizes disk activity (like launching an app) will suffer. There are undoubtedly "timers" which need tweaking. --- just a couple of things which cross my mind at the moment.
However, this is much to long. I hope I've helped folks understand what is happening and how to sort the real Bugs from the "expectation" ones.