ISP + PPA current draw while actively processing a frame — not finding this in the datasheet or TRM

[kungfuartist]

I'm designing a battery-powered application using the ESP32-P4 with a MIPI-CSI camera (GC2053, 1080p, MIPI 2-lane), and I need a reliable current/power budget for the ISP and PPA blocks specifically while they're actively processing a frame (demosaic, lens/distortion correction, scaling).

What I've already checked:

The datasheet's Table 5-7 (Current Consumption in Active Mode) gives CPU current at various frequencies/workloads (WAITI, CoreMark, 32-bit data access), with "Typ¹" (peripheral clocks disabled) and "Typ²" (peripheral clocks enabled) columns — but the test conditions don't mention the ISP or PPA being active, so I believe this reflects CPU-only current with the image hardware idle, not a real camera-processing workload.
I haven't been able to find an ISP- or PPA-specific current figure in the public datasheet, the hardware design guidelines, or what TRM material I could access.

Specific questions:

- Is there a published current/power figure for the ISP block while actively processing (e.g., running demosaic + lens correction on a 1080p RAW10 frame)?
- Same question for the PPA block while actively scaling/converting a frame.
- Does the "peripheral clocks enabled" delta in Table 5-7 (Typ² minus Typ¹) include ISP/PPA power draw, or is that delta something else (e.g., other peripheral domains)?
- If no datasheet figure exists, can anyone share a real bench-measured total system current (P4 + camera) while actively streaming/processing frames — even an approximate number would help me put a realistic ceiling on this rather than guessing.

Context if it's useful: MIPI 2-lane input from GC2053, targeting a low FPS/burst-capture use case (not continuous 30fps streaming), so I care about per-frame active current more than a sustained-streaming average.

Thanks in advance — this is the one number blocking me from finalizing a power budget for a battery-powered design.