1.
This is too specific to add as a default functionality. There's also the problem to specify who is an admin and who is an editor. All access is defined by roles and the role names only have meaning to humans, for instance which policy should a user have to be declared admin or editor.
Besides it can be done by creating custom edit templates (like we've done on ez.no) you then check if a user is part of a specific role (by id) and then show/hide som input fields.
2. Export/import of classes and objects are planned but there's not been any time left to do it yet. We will see if we get the time to do it for a 3.2 or 3.3 release.