The few items you listed should be obtainable with cwcli: http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_resource_manager_essentials/4.0/user/guide/cwcli.pdf
"CLI framework (cwcli) offers remote access facilities to allow you to invoke
cwcli
commands from the client in the same way as they run on the RME server.The name of the servlet is /rme/cwcli.
The following is the servlet to be invoked to execute any command:
For post request,
http://
http://
rme-server:rme-port/rme/cwcli payload XML file
For get request,
http://
http://
rme-server:rme-port/rme/cwcli?command=cwcli config commandname -u user -p BAse64 encoded pwd -args1 arg1value..."
If you're on LMS 3.2, there's even more flexibility with the intro of "Open Database Schema Support":
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/database_schema/guide/dbviews.html#wp67346
Serial number in CMDB has been a sore spot here (though not using LMS as source), because there's no single OID for storing it across Cisco hardware and the CMDB sw vendor doesn't bother doing more than that. I imagine that's why there's a "User_Defined_Serial_Number" column in RME Device_Inventory View Details ("Open Database Schema Support" link above), because it surely will need to be populated manually somehow.