Hm, does you code need to run within Meteor.startup?
Furthermore, I now wonder if wrapping that code within a setTimeout (not a meteor.settimeout though) with 0 delay would somehow trick the process to break out of the fiber, hmm…
Or perhaps Future.detach could be a starting point…
Or you could just create a separate small node app and deploy it as a microservice that the main app can consume over rest, or even ddp with some additional work.