It does strike me that 1,820 individual LEDs is a lot of LEDs. Have you priced out those LEDs? Will you blind people nearby if all of the LEDs are turned on at a time.
That many LEDs are going to need a lot of power. Have you factored into this how many batteries you are going to need, and how long do they need to be powered?
If you use APA102 (Adafruit Dotstars) or WS2812B (Adafruit Neopixels) you are getting to the point where you need complex programming such as the FastLED or Octows2811 libraries.
Instead of APA102/WS2812B LEDS, if you were to go to i2c to drive those LEDs with something like a MCP23017 (drive 16 LEDs via i2c), you would likely not be able to hook these up on a single i2c bus. If the LEDs are the individual LEDs that you buy in combo packs, have you consider how long it will take to solder all of the LEDs and their resistors?
Given your description of different zones, I suspect the best approach is to make it modular. Have one microprocessor (maybe a Teensy LC) to handle each read. I.e. one for the left arm, one for the right leg, etc. Then have them communicate with a boss microprocessor that says 'right leg do pattern #1, head do pattern #7, left arm turn off'. That way, it is much simpler to debug when something goes awry. You can probably use one battery for the processor and the lights that it controls. It also means you don't have to use complex programming like you would if you only used a single processor.
Even if you break the LEDs into several regions, I would look seriously at reducing the number of LEDs. Maybe a 100 or so.