I don't think this can be done in the standard, but you could link in a bespoke BAPI to avoid changing the standard one.
Based on my notes I've used standard BAPIs "BAPI_EMPLCOMM_CHANGE" and "BAPI_EMPLCOMM_CREATE" from IdM/Maxware JavaScript to update the 0105 infotype fields one by one.
(if I remember correctly the reason for using the BAPIs instead of IdM's standard was that I wasn't able to change the SYSUNAME in 0105 for some reason for the other attributes the standard worked just fine.)
The trick with the change-BAPI is that the validity dates for the new and old value cannot overlap. So, the old dates must be fetched with "BAPI_EMPLCOMM_GETLIST". But how the BAPIs work can/should be tested with ABAP Workbench before any code is written.