Three suggestions.
Most of what you're going for from that basic list are either system variables (@@servername, @@version, etc.) or can be accessed from the sp_configure query. So yeah, getting that information is pretty straight forward.
Why on earth, when you're already using & supporting SQL Server, would you put the data into Access? Just store it in a SQL Server database?
I'd suggest looking at this as an opportunity to start learning PowerShell as a means for trolling through your servers to run these queries. It'll make automating the process a heck of a lot easier.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning