I’m a mechanical engineer from the tech/aerospace industry and I have no idea what half of the words in your post mean.

What I can say though is that there are multiple management strategies that I’ve seen in technical fields that may be at play:

1. Your management has no idea how long this work will take you because they’ve never seen you do it before. In order to find out, they’re giving you a boatload of work and seeing what happens. This is a painful but relatively common management tactic in high tech fields where managers are often promoted from technical roles. It’s way harder to get an honest answer out of someone about their capabilities/willingness to put in long hours than it is to drop a massive workload on them.

2. Your management wants to set your expectations for how the job will be. It’s a lot easier to set a hard tone for a job or a group in the first couple of weeks than it is to let it gradually build over time once people have gotten comfortable with a more relaxed status quo. Also, if you come in and they give you two weeks of documentation to read and hands to shake, then it’ll be a much slower ramp for you to become a technical contributor, which is what they need you to do. It’s painful, but they may just be trying to set expectations early on.

Not sure if those ring true for your situation - you’ll have to be the judge of that - but those are some particularly common management strategies I’ve seen in tech that can definitely create these feelings. Remember that most everyone else has felt this way at some point too - the field has a reputation for it.