Apart from any consistency problems mentioned elsewhere, this approach really just hides the problem rather than solving it.
It still has many values behind 1 (or 3) attribute files. If the "one value per file" policy stands, it is the wrong thing to do. If the "one value per file" policy can be extended to support arbitrarily large values, then implementing that policy extension through seqfile or similar would be a much more sensible resolution.