please clarify the DB situation - are you planing the exact same CMS DB for 4.1 or are you planning to have new CMS DB for 4.1 in the same DB as 4.0 CMS DB ?
Normally, the approach in this scenario is to build new 4.1 environment and then move content using promotion management.
If you're planing to have same CMS DB for 4.1 as one for 4.0 , you can't do that, since 4.0 CMS DB has to be upgraded first and once its upgraded it can't be used for 4.0.
So, other method would be to upgrade current system to 4.1 or better yet 4.2 and then add new node on the new server to it at the same patch level, then retire/delete original node, leaving new server with original cms db in place and no need to use prom management.