claude-code sdk mode (-p) has a very long warm up time on slower devices

I'm running claude-code sdk on a raspberry pi 4b. Functionally it works, but the reported API time is far less than the wall clock time. For a simple request
claude -p "say hello and nothing else this is a latency test"
I get a reported time of ~3 seconds and a wall clock time of ~20 seconds.

I'd really love a way to embed claude in my app, but in a way where I can keep it "warm". The --resume and --continue feature works, but the startup time is still problematic. I believe the bulk of the time goes to rebuilding the initial context but it's not very clear. Even with the --debug flag its hard to pin down what makes it so slow to use in this way.

The feature request: to be more specific, it would be great if there was a way to use the -p mode on a claude-code process that is already running in the background of my app.

Thanks.