As for the pictures - I'm comfortable with them being Base64-encoded and encapsulated at the end of the FB2 file.
EPUB indeed is more feature reach but from my point of view that is all bloat and unnecessary complexity.
I haven't seen a single ebook which could actually benefit from EPUB features. Whatever features rich typesetting worth saving is rarely published this way anyway, they just use PDF (which is sad but true).
HTML also allows you to specify an image inline using Base64 encoding; soemthing like
<img src="data:image/png;base64, fhfhfhfh...">
I don't know what FB2 does, but it's definitely a solvable problem.[1]: https://en.wikipedia.org/wiki/FictionBook#Differences_from_o...
I recently bought an ebook and found that it was formatted in a custom font, so I "returned" it immediately. I guess this is a philosophical issue to some extent, but I don't think the typical novel is visual content, and I don't know what you're trying to accomplish by overriding my preferred settings for text presentation.
Besides, there's a big surface for bugs in epub. It happened to me to buy an ebook which froze my reader until I weeded out CSS, and fonts from it with Calibre. Ironically, it also, made it easier to read.
It's made for readers by readers, so no DRM. A non-starter for publishing corporations, sadly.
Page numbers can indeed be very useful for the purpose of non-electronic referencing of pieces of a text, especially if a printed edition of the book exists you need to collaborate with people having such but I would rather use simple anchor tags for this.